# Severe : Could not contact the Allmon3 Manager

**URL:** <https://community.allstarlink.org/t/severe-could-not-contact-the-allmon3-manager/20167>\
**Category:** AllStarLink\
**Tags:** allmon3\
**Created:** [May 24, 2023, 7:13pm UTC](https://community.allstarlink.org/t/severe-could-not-contact-the-allmon3-manager/20167 "2023-05-24T19:13:42Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![kf0fyc](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/5f9b8f/32.png) [@kf0fyc](https://community.allstarlink.org/u/kf0fyc)\
**Post date:** [May 24, 2023, 7:13pm UTC](https://community.allstarlink.org/t/severe-could-not-contact-the-allmon3-manager/20167/1 "2023-05-24T19:13:42Z")

</div>

I too have a little issue with Configuring my Nodes as when I do load the URL is says.

Severe : Could not contact the Allmon3 Manager.

I think its because I dont have a /etc/allmon3/user folder but Its work in Progress which I am working on…

I’m using the Allstar 2.0 on a x64 Server…

Thanks

Rob…

---

<div class="post-metadata">

**Author:** ![WD6AWP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/32/5_2.png) [@WD6AWP](https://community.allstarlink.org/u/WD6AWP)\
**Post date:** [May 24, 2023, 10:11pm UTC](https://community.allstarlink.org/t/severe-could-not-contact-the-allmon3-manager/20167/2 "2023-05-24T22:11:52Z")

</div>

I didn’t have a users file upon installing 0.10 either. Just `touch /etc/allmon3/users` and then create a user per the README. That will fix the user issue.

I also didn’t have a menu.ini. I thought maybe I did something wrong because the package manager said those files got installed.

If you don’t have a menu.ini.example grab [Allmon3/menu.ini.example at develop · AllStarLink/Allmon3 · GitHub](https://github.com/AllStarLink/Allmon3/blob/develop/conf/menu.ini.example) rename it to menu.ini and configure it per the comments.

---

<div class="post-metadata">

**Author:** ![kf0fyc](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/5f9b8f/32.png) [@kf0fyc](https://community.allstarlink.org/u/kf0fyc)\
**Post date:** [May 24, 2023, 11:45pm UTC](https://community.allstarlink.org/t/severe-could-not-contact-the-allmon3-manager/20167/3 "2023-05-24T23:45:38Z")

</div>

Yeah tried to simply add a user using the allmon2-passwd command and I get the Following

When I create a users folder

Traceback (most recent call last):  
File “/usr/bin/allmon3-passwd”, line 46, in   
with open(user\_filename, newline=“”) as user\_file:  
IsADirectoryError: [Errno 21] Is a directory: ‘/etc/allmon3/users’

When I remove the folder

Traceback (most recent call last):  
File “/usr/bin/allmon3-passwd”, line 46, in   
with open(user\_filename, newline=“”) as user\_file:  
FileNotFoundError: [Errno 2] No such file or directory: ‘/etc/allmon3/users’

I’m guessing the issue is me…

lol

Rob…

---

<div class="post-metadata">

**Author:** ![WD6AWP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/32/5_2.png) [@WD6AWP](https://community.allstarlink.org/u/WD6AWP)\
**Post date:** [May 25, 2023, 2:19am UTC](https://community.allstarlink.org/t/severe-could-not-contact-the-allmon3-manager/20167/4 "2023-05-25T02:19:50Z")

</div>

Users is a file not a folder. You have to create the file with the touch command…  
However, **if** there’s a users directory you have to remove it:

```auto
cd /etc/allmon3
sudo rm users

```

Create the user file:  
`sudo touch /etc/allmon3/users`

Then add your admin (and/or other) user:  
`sudo allmon3-passwd admin`

---

<div class="post-metadata">

**Author:** ![kf0fyc](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/5f9b8f/32.png) [@kf0fyc](https://community.allstarlink.org/u/kf0fyc)\
**Post date:** [May 25, 2023, 5:18am UTC](https://community.allstarlink.org/t/severe-could-not-contact-the-allmon3-manager/20167/5 "2023-05-25T05:18:14Z")

</div>

Well who says you cant teach Grandpa how to suck eggs ?..

Thanks for the Re-Education…

Told ya it was Prob me…

Now just need to fix the following and hopefully I am Golden…

SEVERE: Could not contact the allmon3 manager. Check the allmon3 service, webserver config, and reload the window.

Thanks

Rob…

---

<div class="post-metadata">

**Author:** ![WD6AWP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/32/5_2.png) [@WD6AWP](https://community.allstarlink.org/u/WD6AWP)\
**Post date:** [May 25, 2023, 1:38pm UTC](https://community.allstarlink.org/t/severe-could-not-contact-the-allmon3-manager/20167/6 "2023-05-25T13:38:40Z")

</div>

You didn’t need to worry about users yet, but that’s ok. It’s fixed now. 🙂

First thing to work on is getting the Allmon3 service to login to the Asterisk Manager.

- Edit the /etc/allmon3/allmon3.ini file and set the user ID and password to match the user ID and password in /etc/asterisk/manager.ini
- Restart the service. As root to sudo: `systemctl restart allmon3.service`
- Check that the service is running w/o errors. As root to sudo: `systemctl status allmon3.service`

---

<div class="post-metadata">

**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\
**Post date:** [May 25, 2023, 2:04pm UTC](https://community.allstarlink.org/t/severe-could-not-contact-the-allmon3-manager/20167/7 "2023-05-25T14:04:45Z")

</div>

Added an issue:

> <https://github.com/AllStarLink/Allmon3/issues/124>
>
> On installation, the .deb file is not consistently installing at least \`/etc/all…mon3/users\` and \`/etc/allmon3/menu.ini.example\`.

---

<div class="post-metadata">

**Author:** ![kf0fyc](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/5f9b8f/32.png) [@kf0fyc](https://community.allstarlink.org/u/kf0fyc)\
**Post date:** [May 26, 2023, 4:27pm UTC](https://community.allstarlink.org/t/severe-could-not-contact-the-allmon3-manager/20167/8 "2023-05-26T16:27:37Z")

</div>

systemctl status allmon3 gives me the Following even though aiohttp is satisfied

allmon3.service - Allmon3 daemon  
Loaded: loaded (/lib/systemd/system/allmon3.service; enabled; vendor preset: enabled)  
Active: failed (Result: exit-code) since Fri 2023-05-26 11:23:57 CDT; 1min 57s ago  
Process: 291 ExecStart=/usr/bin/allmon3 (code=exited, status=1/FAILURE)  
Main PID: 291 (code=exited, status=1/FAILURE)

May 26 11:23:56 1200Node systemd[1]: Starting Allmon3 daemon…  
May 26 11:23:56 1200Node systemd[1]: Started Allmon3 daemon.  
May 26 11:23:57 1200Node allmon3[291]: Traceback (most recent call last):  
May 26 11:23:57 1200Node allmon3[291]: File “/usr/bin/allmon3”, line 18, in   
May 26 11:23:57 1200Node allmon3[291]: from asl\_allmon import allmon3\_server, allmon3\_ws\_status, allmon3\_ws\_cmd, allmon3\_ws\_voter  
May 26 11:23:57 1200Node allmon3[291]: File “/usr/lib/python3/dist-packages/asl\_allmon/allmon3\_server/ **init**.py”, line 8, in \<modu  
May 26 11:23:57 1200Node allmon3[291]: from aiohttp import web  
May 26 11:23:57 1200Node allmon3[291]: ModuleNotFoundError: No module named ‘aiohttp’  
May 26 11:23:57 1200Node systemd[1]: allmon3.service: Main process exited, code=exited, status=1/FAILURE  
May 26 11:23:57 1200Node systemd[1]: allmon3.service: Failed with result ‘exit-code’.

---

<div class="post-metadata">

**Author:** ![kf0fyc](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/5f9b8f/32.png) [@kf0fyc](https://community.allstarlink.org/u/kf0fyc)\
**Post date:** [May 26, 2023, 5:02pm UTC](https://community.allstarlink.org/t/severe-could-not-contact-the-allmon3-manager/20167/9 "2023-05-26T17:02:41Z")

</div>

repeater@1200Node:~$ pip3 show aiohttp  
Name: aiohttp  
Version: 3.8.4  
Summary: Async http client/server framework (asyncio)  
Home-page: [GitHub - aio-libs/aiohttp: Asynchronous HTTP client/server framework for asyncio and Python](https://github.com/aio-libs/aiohttp)  
Author: None  
Author-email: None  
License: Apache 2  
Location: /home/repeater/.local/lib/python3.7/site-packages  
Requires: yarl, asynctest, attrs, frozenlist, charset-normalizer, multidict, typing-extensions, aiosignal, async-timeout  
Required-by:

---

<div class="post-metadata">

**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\
**Post date:** [May 26, 2023, 6:55pm UTC](https://community.allstarlink.org/t/severe-could-not-contact-the-allmon3-manager/20167/10 "2023-05-26T18:55:19Z")

</div>

Installing the pip modules to a `.local` directory isn’t likely to work for another user. The daemon runs as the user allmon3. Can you install the pip modules as root into the system-wide `dist-packages` or `site-packages` locations?

As root do something like this:

```auto
$ python3
Python 3.9.2 (default, Feb 28 2021, 17:03:44)
[GCC 10.2.1 20210110] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> print(sys.path)
['', '/usr/lib/python39.zip', '/usr/lib/python3.9', '/usr/lib/python3.9/lib-dynload', '/usr/local/lib/python3.9/dist-packages', '/usr/lib/python3/dist-packages']
>>>

```

For system daemons, the python package dependencies must be in the default import paths.

---

<div class="post-metadata">

**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\
**Post date:** [May 26, 2023, 9:45pm UTC](https://community.allstarlink.org/t/severe-could-not-contact-the-allmon3-manager/20167/12 "2023-05-26T21:45:39Z")

</div>

But you have to do it as the root user. From the “$” prompt, it tells me you’re using a non-root account.

---

<div class="post-metadata">

**Author:** ![kf0fyc](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/5f9b8f/32.png) [@kf0fyc](https://community.allstarlink.org/u/kf0fyc)\
**Post date:** [May 26, 2023, 10:03pm UTC](https://community.allstarlink.org/t/severe-could-not-contact-the-allmon3-manager/20167/13 "2023-05-26T22:03:13Z")

</div>

repeater@1200Node:~$ su  
Password:  
root@1200Node:/home/repeater# python3  
Python 3.7.3 (default, Oct 31 2022, 14:04:00)  
[GCC 8.3.0] on linux  
Type “help”, “copyright”, “credits” or “license” for more information.

> > > import sys  
> > > print (sys.path)  
> > > [‘’, ‘/usr/lib/python37.zip’, ‘/usr/lib/python3.7’, ‘/usr/lib/python3.7/lib-dynload’, ‘/usr/local/lib/python3.7/dist-packages’, ‘/usr/lib/python3/dist-packages’]

---

<div class="post-metadata">

**Author:** ![kf0fyc](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/5f9b8f/32.png) [@kf0fyc](https://community.allstarlink.org/u/kf0fyc)\
**Post date:** [May 26, 2023, 10:03pm UTC](https://community.allstarlink.org/t/severe-could-not-contact-the-allmon3-manager/20167/14 "2023-05-26T22:03:59Z")

</div>

I removed the earlier post

---

<div class="post-metadata">

**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\
**Post date:** [May 26, 2023, 10:05pm UTC](https://community.allstarlink.org/t/severe-could-not-contact-the-allmon3-manager/20167/15 "2023-05-26T22:05:18Z")

</div>

Right. So notice that your pip3 library path of /home/repeater/.local/lib is not longer available. You need to install the python dependencies as root so they and up in the correct site-packages location globally. That’s why allmon3 won’t start.

---

<div class="post-metadata">

**Author:** ![kf0fyc](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/5f9b8f/32.png) [@kf0fyc](https://community.allstarlink.org/u/kf0fyc)\
**Post date:** [May 26, 2023, 10:52pm UTC](https://community.allstarlink.org/t/severe-could-not-contact-the-allmon3-manager/20167/16 "2023-05-26T22:52:20Z")

</div>

Ok well might give this up for a while…  
allmon3.service - Allmon3 daemon  
Loaded: loaded (/lib/systemd/system/allmon3.service; enabled; vendor preset: en  
Active: failed (Result: exit-code) since Fri 2023-05-26 17:47:59 CDT; 34s ago  
Process: 9071 ExecStart=/usr/bin/allmon3 (code=exited, status=1/FAILURE)  
Main PID: 9071 (code=exited, status=1/FAILURE)

May 26 17:47:59 1200Node systemd[1]: Starting Allmon3 daemon…  
May 26 17:47:59 1200Node systemd[1]: Started Allmon3 daemon.  
May 26 17:47:59 1200Node allmon3[9071]: Traceback (most recent call last):  
May 26 17:47:59 1200Node allmon3[9071]: File “/usr/bin/allmon3”, line 18, in \<mo  
May 26 17:47:59 1200Node allmon3[9071]: from asl\_allmon import allmon3\_server,  
May 26 17:47:59 1200Node allmon3[9071]: File "/usr/lib/python3/dist-packages/asl  
May 26 17:47:59 1200Node allmon3[9071]: from aiohttp\_session import get\_sessio  
May 26 17:47:59 1200Node allmon3[9071]: ModuleNotFoundError: No module named 'aioh  
May 26 17:47:59 1200Node systemd[1]: allmon3.service: Main process exited, code=ex  
May 26 17:47:59 1200Node systemd[1]: allmon3.service: Failed with result 'exit-cod

root@1200Node:/home/repeater# nano /etc/allmon3/web.iniroot@1200Node:/home/repeater# python3  
Python 3.7.3 (default, Oct 31 2022, 14:04:00)  
[GCC 8.3.0] on linux  
Type “help”, “copyright”, “credits” or “license” for more information.

> > > import sys  
> > > print (sys.path)  
> > > [‘’, ‘/usr/lib/python37.zip’, ‘/usr/lib/python3.7’, ‘/usr/lib/python3.7/lib-dynload’, ‘/usr/local/lib/python3.7/dist-packages’, ‘/usr/lib/python3/dist-packages’]

Used root and the issue still wont go away…

---

<div class="post-metadata">

**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\
**Post date:** [May 26, 2023, 11:32pm UTC](https://community.allstarlink.org/t/severe-could-not-contact-the-allmon3-manager/20167/17 "2023-05-26T23:32:35Z")

</div>

As root, what is the output of `pip3 show aiohttp` and `pip3 show aiohttp_session`? You should see something like:

```auto
# pip3 show aiohttp
Name: aiohttp
Version: 3.8.4
Summary: Async http client/server framework (asyncio)
Home-page: https://github.com/aio-libs/aiohttp
Author: None
Author-email: None
License: Apache 2
Location: /usr/local/lib/python3.7/dist-packages
Requires: asynctest, multidict, attrs, frozenlist, typing-extensions, charset-normalizer, yarl, aiosignal, async-timeout
Required-by: aiohttp-session

# pip3 show aiohttp_session
Name: aiohttp-session
Version: 2.12.0
Summary: sessions for aiohttp.web
Home-page: https://github.com/aio-libs/aiohttp_session/
Author: Andrew Svetlov
Author-email: andrew.svetlov@gmail.com
License: Apache 2
Location: /usr/local/lib/python3.7/dist-packages
Requires: aiohttp, typing-extensions
Required-by:

```

---

<div class="post-metadata">

**Author:** ![kf0fyc](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/5f9b8f/32.png) [@kf0fyc](https://community.allstarlink.org/u/kf0fyc)\
**Post date:** [May 27, 2023, 12:10am UTC](https://community.allstarlink.org/t/severe-could-not-contact-the-allmon3-manager/20167/18 "2023-05-27T00:10:08Z")

</div>

pip3 show aiohttp does show the same but does not have an entry on Required-by …

pip3 show aiohttp\_session shows nothing…

---

<div class="post-metadata">

**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\
**Post date:** [May 27, 2023, 1:19pm UTC](https://community.allstarlink.org/t/severe-could-not-contact-the-allmon3-manager/20167/19 "2023-05-27T13:19:19Z")

</div>

Then you didn’t install `aiohttp_session`. If you install that with `pip3`, it should start.

---

<div class="post-metadata">

**Author:** ![kf0fyc](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/5f9b8f/32.png) [@kf0fyc](https://community.allstarlink.org/u/kf0fyc)\
**Post date:** [May 27, 2023, 6:23pm UTC](https://community.allstarlink.org/t/severe-could-not-contact-the-allmon3-manager/20167/20 "2023-05-27T18:23:30Z")

</div>

Maybe I missed that Instruction on the Install or maybe its because Im using the PC based version on Allstarlink  
allmon3.service - Allmon3 daemon  
Loaded: loaded (/lib/systemd/system/allmon3.service; enabled; vendor preset: enabled)  
Active: failed (Result: exit-code) since Sat 2023-05-27 13:20:18 CDT; 1s ago  
Process: 29105 ExecStart=/usr/bin/allmon3 (code=exited, status=1/FAILURE)  
Main PID: 29105 (code=exited, status=1/FAILURE)

May 27 13:20:17 1200Node allmon3[29105]: asyncio.run(start\_tasks())  
May 27 13:20:17 1200Node allmon3[29105]: File “/usr/lib/python3.7/asyncio/runners.py”, line 43, in run  
May 27 13:20:17 1200Node allmon3[29105]: return loop.run\_until\_complete(main)  
May 27 13:20:17 1200Node allmon3[29105]: File “/usr/lib/python3.7/asyncio/base\_events.py”, line 584, in run\_until\_complete  
May 27 13:20:17 1200Node allmon3[29105]: return future.result()  
May 27 13:20:17 1200Node allmon3[29105]: File “/usr/bin/allmon3”, line 97, in start\_tasks  
May 27 13:20:17 1200Node allmon3[29105]: except asyncio.exceptions.CancelledError as e:  
May 27 13:20:17 1200Node allmon3[29105]: AttributeError: module ‘asyncio’ has no attribute ‘exceptions’  
May 27 13:20:18 1200Node systemd[1]: allmon3.service: Main process exited, code=exited, status=1/FAILURE  
May 27 13:20:18 1200Node systemd[1]: allmon3.service: Failed with result ‘exit-code’.

ok pip3 Install aiohttp\_session

now status gives me…

---

<div class="post-metadata">

**Author:** ![WD6AWP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/32/5_2.png) [@WD6AWP](https://community.allstarlink.org/u/WD6AWP)\
**Post date:** [May 27, 2023, 9:08pm UTC](https://community.allstarlink.org/t/severe-could-not-contact-the-allmon3-manager/20167/21 "2023-05-27T21:08:51Z")

</div>

What does your /etc/allmon3/allmon3.ini look like?  
What does you /etc/asterisk/manager.ini look like?

Be sure not to post any passwords.

[Next page](https://community.allstarlink.org/t/severe-could-not-contact-the-allmon3-manager/20167.md?page=2)