adam/meshing-around
1
0 Fork 0
mirror of https://github.com/SpudGunMan/meshing-around.git synced 2026-11-03 07:22:23 +01:00
Code Issues 12 Packages Projects Releases Wiki Activity

How to properly use? Errors while running. #65

New Issue
Closed
opened 2026-10-05 01:19:00 +02:00 by adam · 7 comments
adam commented 2026-10-05 01:19:00 +02:00
Owner
Copy link
Copy source

Helllo,
I'm not sure if I'm just stupid or if I'm missing some information..
So I did the quick install with the Install.sh, on my RaspberryPi 3B with Raspbian Lite.

I want to connect through BLE to a Heltec V3 and have this bot be sort of an Auto responder or just a fun thing to test distances etc.

I changed the config.ini
I tried the ./launch.sh html5 this generated a page.
But gave some warnings?

./launch.sh html5
Checking log file: /opt/meshing-around/logs/meshbot.log
Consumed 54577 lines from /opt/meshing-around/logs/meshbot.log
Node1: N/A N/A N/A
Node2: N/A N/A N/A
Warning issue reading database file: [Errno 2] No such file or directory: '/opt/meshing-around/data/lemonstand_hs.pkl'
Warning issue reading database file: [Errno 2] No such file or directory: '/opt/meshing-around/data/dopewar_hs.pkl'
Warning issue reading database file: [Errno 2] No such file or directory: '/opt/meshing-around/data/blackjack_hs.pkl'
Warning issue reading database file: [Errno 2] No such file or directory: '/opt/meshing-around/data/videopoker_hs.pkl'
Warning issue reading database file: [Errno 2] No such file or directory: '/opt/meshing-around/data/mmind_hs.pkl'
Warning issue reading database file: [Errno 2] No such file or directory: '/opt/meshing-around/data/golfsim_hs.pkl'
Warning issue reading database file: [Errno 2] No such file or directory: '/opt/meshing-around/data/qrz.db'


MeshBot (BBS) Web Dashboard Report Generator

Main dashboard: file:///opt/meshing-around/etc/www/index.html

Existing index.html backed up to /opt/meshing-around/etc/www/index_backup_2025-07-28.html
Main dashboard written to /opt/meshing-around/etc/www/index.html
HTML reports generated for 2025-07-28 in /opt/meshing-around/etc/www

My logs however give me the following error:

mac = 34:B7:DA:62:84:59 not supported. Validate your config against config.template Exiting
2025-07-28 16:11:07,231 |    DEBUG | System: Initializing Interfaces
2025-07-28 16:11:07,232 | CRITICAL | System: Interface Type: ble

And when running the update.sh to try and fix stuff, I got the following errors:
Failed to start pong_bot.service: Unit pong_bot.service not found.
Failed to start mesh_bot_reporting.service: Unit mesh_bot_reporting.service not found.
Failed to start mesh_bot_w3.service: Unit mesh_bot_w3.service not found.

If I try to run the `./launch.sh meshbot I also get some python errors:

(venv) thursten@MeshtasticPi:/opt/meshing-around $ ./launch.sh meshbot
Traceback (most recent call last):
  File "/opt/meshing-around/mesh_bot.py", line 14, in <module>
    from modules.log import *
  File "/opt/meshing-around/modules/log.py", line 72, in <module>
    file_handler_sys = TimedRotatingFileHandler('logs/meshbot.log', when='midnight', backupCount=log_backup_count, encoding='utf-8')
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/logging/handlers.py", line 214, in __init__
    BaseRotatingHandler.__init__(self, filename, 'a', encoding=encoding,
  File "/usr/lib/python3.11/logging/handlers.py", line 58, in __init__
    logging.FileHandler.__init__(self, filename, mode=mode,
  File "/usr/lib/python3.11/logging/__init__.py", line 1181, in __init__
    StreamHandler.__init__(self, self._open())
                                 ^^^^^^^^^^^^
  File "/usr/lib/python3.11/logging/__init__.py", line 1213, in _open
    return open_func(self.baseFilename, self.mode,
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
PermissionError: [Errno 13] Permission denied: '/opt/meshing-around/logs/meshbot.log'

I'm not sure if I also need to follow the docker steps instead of running it in the Python venv.

I'm sorry it's mostly a Info dump, if you need any extra info let me know.

I also am not sure how to connect to a chat or any other configs of the Heltec Device.

Thanks in advance.

Helllo, I'm not sure if I'm just stupid or if I'm missing some information.. So I did the quick install with the Install.sh, on my RaspberryPi 3B with Raspbian Lite. I want to connect through BLE to a Heltec V3 and have this bot be sort of an Auto responder or just a fun thing to test distances etc. I changed the config.ini I tried the `./launch.sh html5` this generated a page. But gave some warnings? ``` ./launch.sh html5 Checking log file: /opt/meshing-around/logs/meshbot.log Consumed 54577 lines from /opt/meshing-around/logs/meshbot.log Node1: N/A N/A N/A Node2: N/A N/A N/A Warning issue reading database file: [Errno 2] No such file or directory: '/opt/meshing-around/data/lemonstand_hs.pkl' Warning issue reading database file: [Errno 2] No such file or directory: '/opt/meshing-around/data/dopewar_hs.pkl' Warning issue reading database file: [Errno 2] No such file or directory: '/opt/meshing-around/data/blackjack_hs.pkl' Warning issue reading database file: [Errno 2] No such file or directory: '/opt/meshing-around/data/videopoker_hs.pkl' Warning issue reading database file: [Errno 2] No such file or directory: '/opt/meshing-around/data/mmind_hs.pkl' Warning issue reading database file: [Errno 2] No such file or directory: '/opt/meshing-around/data/golfsim_hs.pkl' Warning issue reading database file: [Errno 2] No such file or directory: '/opt/meshing-around/data/qrz.db' MeshBot (BBS) Web Dashboard Report Generator Main dashboard: file:///opt/meshing-around/etc/www/index.html Existing index.html backed up to /opt/meshing-around/etc/www/index_backup_2025-07-28.html Main dashboard written to /opt/meshing-around/etc/www/index.html HTML reports generated for 2025-07-28 in /opt/meshing-around/etc/www ``` My logs however give me the following error: ``` mac = 34:B7:DA:62:84:59 not supported. Validate your config against config.template Exiting 2025-07-28 16:11:07,231 | DEBUG | System: Initializing Interfaces 2025-07-28 16:11:07,232 | CRITICAL | System: Interface Type: ble ``` And when running the update.sh to try and fix stuff, I got the following errors: `Failed to start pong_bot.service: Unit pong_bot.service not found.` `Failed to start mesh_bot_reporting.service: Unit mesh_bot_reporting.service not found.` `Failed to start mesh_bot_w3.service: Unit mesh_bot_w3.service not found.` If I try to run the `./launch.sh meshbot I also get some python errors: ``` (venv) thursten@MeshtasticPi:/opt/meshing-around $ ./launch.sh meshbot Traceback (most recent call last): File "/opt/meshing-around/mesh_bot.py", line 14, in <module> from modules.log import * File "/opt/meshing-around/modules/log.py", line 72, in <module> file_handler_sys = TimedRotatingFileHandler('logs/meshbot.log', when='midnight', backupCount=log_backup_count, encoding='utf-8') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/logging/handlers.py", line 214, in __init__ BaseRotatingHandler.__init__(self, filename, 'a', encoding=encoding, File "/usr/lib/python3.11/logging/handlers.py", line 58, in __init__ logging.FileHandler.__init__(self, filename, mode=mode, File "/usr/lib/python3.11/logging/__init__.py", line 1181, in __init__ StreamHandler.__init__(self, self._open()) ^^^^^^^^^^^^ File "/usr/lib/python3.11/logging/__init__.py", line 1213, in _open return open_func(self.baseFilename, self.mode, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ PermissionError: [Errno 13] Permission denied: '/opt/meshing-around/logs/meshbot.log' ``` I'm not sure if I also need to follow the docker steps instead of running it in the Python venv. I'm sorry it's mostly a Info dump, if you need any extra info let me know. I also am not sure how to connect to a chat or any other configs of the Heltec Device. Thanks in advance. <!-- github-sync-id:3270223306 -->
adam closed this issue 2026-10-05 01:19:00 +02:00
adam commented 2026-10-05 01:19:01 +02:00
Author
Owner
Copy link
Copy source

Did you install first?

Readme.md has some steps a few major ways

Install.sh will guide you through as well.

Can't generate the html till the bot runs a little.

Did you install first? Readme.md has some steps a few major ways Install.sh will guide you through as well. Can't generate the html till the bot runs a little. <!-- github-comment-id:3129190285 -->
adam commented 2026-10-05 01:19:02 +02:00
Author
Owner
Copy link
Copy source

Did you install first?

Readme.md has some steps a few major ways

Install.sh will guide you through as well.

Can't generate the html till the bot runs a little.

Hey man, thanks for reaching out!

Yeah so what I did basically is do the git clone, than ran the install.sh, it asked to install in /op/meshing-around/ so I did.
went through all the questions in the script. and it all seemed fine.

However I'm kind of lost as to how to actually connect my Heltec and than have the bot do stuff, like how do I connect from my other Meshtastic devices to the Heltec and Bot on the Pi?
Say from a Lilygo T-deck Plus for example.

I almost feel like I missed some installation steps with the amount of errors I got above.

Just to be clear, you can use the ./install.sh OR the docker right? It's not AND docker. cause I didn't do that.

> Did you install first? > > Readme.md has some steps a few major ways > > Install.sh will guide you through as well. > > Can't generate the html till the bot runs a little. Hey man, thanks for reaching out! Yeah so what I did basically is do the git clone, than ran the install.sh, it asked to install in /op/meshing-around/ so I did. went through all the questions in the script. and it all seemed fine. However I'm kind of lost as to how to actually connect my Heltec and than have the bot do stuff, like how do I connect from my other Meshtastic devices to the Heltec and Bot on the Pi? Say from a Lilygo T-deck Plus for example. I almost feel like I missed some installation steps with the amount of errors I got above. Just to be clear, you can use the ./install.sh *OR* the docker right? It's not *AND* docker. cause I didn't do that. <!-- github-comment-id:3129247656 -->
adam commented 2026-10-05 01:19:03 +02:00
Author
Owner
Copy link
Copy source

Install or docker correct on a pi I would not use docker

You should be able to cd to /op/meshing-around/

And launch mesh-bot.py

If you started it as a service it's likely already trying to run

Just edit the config.ini for the proper usb0

Once it's running

Just ping a channel

Install or docker correct on a pi I would not use docker You should be able to cd to /op/meshing-around/ And launch mesh-bot.py If you started it as a service it's likely already trying to run Just edit the config.ini for the proper usb0 Once it's running Just ping a channel <!-- github-comment-id:3130140919 -->
adam commented 2026-10-05 01:19:03 +02:00
Author
Owner
Copy link
Copy source

Install or docker correct on a pi I would not use docker

You should be able to cd to /op/meshing-around/

And launch mesh-bot.py

If you started it as a service it's likely already trying to run

Just edit the config.ini for the proper usb0

Once it's running

Just ping a channel

Okay, okay,
That sounds good!
launch meshbot.py you say?
Does that mean python mesh-bot.py or ./launch.sh meshbot
But if I use that I get the python errors I stated above.

And how do I "Ping a channel" I can't connect to the Meshtastic or setup a DM without a UI? Like Scan a QR code? I'm not really sure how it works.

You also mention "just edit the config.ini for the proper usb0":
Do I have to add that even if using Bluetooth? And how would I find the correct usb0 port for my onboard Bluetooth?

Sorry again, lots of questions, but it is becoming more clear! :)

Okay scratch that, It seems to run now.

However I still can't get the daemon to keep running. somehow the default service that get's created stops or crashes seconds after starting.
It looks like it is because the meshbot.log that get's created or written to has the wrong owner info.

it has thursten:thursten meshbot.log instead of either thursten:meshbot meshbot.log or meshbot:meshbot meshbot.log

Even when the user and group are set in the mesh_bot.service?

> Install or docker correct on a pi I would not use docker > > You should be able to cd to /op/meshing-around/ > > And launch mesh-bot.py > > If you started it as a service it's likely already trying to run > > Just edit the config.ini for the proper usb0 > > Once it's running > > Just ping a channel <s>Okay, okay, That sounds good! launch meshbot.py you say? Does that mean `python mesh-bot.py` or `./launch.sh meshbot` But if I use that I get the python errors I stated above. And how do I "Ping a channel" I can't connect to the Meshtastic or setup a DM without a UI? Like Scan a QR code? I'm not really sure how it works. You also mention "just edit the config.ini for the proper usb0": Do I have to add that even if using Bluetooth? And how would I find the correct usb0 port for my onboard Bluetooth? Sorry again, lots of questions, but it is becoming more clear! :)</s> Okay scratch that, It seems to run now. However I still can't get the daemon to keep running. somehow the default service that get's created stops or crashes seconds after starting. It looks like it is because the meshbot.log that get's created or written to has the wrong owner info. it has `thursten:thursten meshbot.log` instead of either `thursten:meshbot meshbot.log` or `meshbot:meshbot meshbot.log` Even when the user and group are set in the mesh_bot.service? <!-- github-comment-id:3130750841 -->
adam commented 2026-10-05 01:19:04 +02:00
Author
Owner
Copy link
Copy source

Set owner or permission on the log directory the installer should have e done it for you?

Set owner or permission on the log directory the installer should have e done it for you? <!-- github-comment-id:3138329776 -->
adam commented 2026-10-05 01:19:05 +02:00
Author
Owner
Copy link
Copy source

I ran into the same/similar issue, and @SpudGunMan was spot on.

Issue

$ sudo systemctl status mesh_bot.service

× mesh_bot.service - MESH-BOT
     Loaded: loaded (/etc/systemd/system/mesh_bot.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Sun 2025-08-10 23:44:55 PDT; 8min ago
   Duration: 143ms
    Process: 7195 ExecStart=/usr/bin/bash launch.sh mesh (code=exited, status=0/SUCCESS)
    Process: 7198 ExecStop=pkill -f mesh_bot.py (code=exited, status=1/FAILURE)
   Main PID: 7195 (code=exited, status=0/SUCCESS)
        CPU: 126ms

Aug 10 23:44:55 raspberrypi systemd[1]: mesh_bot.service: Scheduled restart job, restart counter is at 5.
Aug 10 23:44:55 raspberrypi systemd[1]: Stopped mesh_bot.service - MESH-BOT.
Aug 10 23:44:55 raspberrypi systemd[1]: mesh_bot.service: Start request repeated too quickly.
Aug 10 23:44:55 raspberrypi systemd[1]: mesh_bot.service: Failed with result 'exit-code'.
Aug 10 23:44:55 raspberrypi systemd[1]: Failed to start mesh_bot.service - MESH-BOT.

Running journalctl to see the stdout/stderr:

$ sudo journalctl -u mesh_bot.service

Aug 10 23:44:54 raspberrypi bash[7193]: PermissionError: [Errno 13] Permission denied: '/opt/meshing-around/logs/meshbot.log'
Aug 10 23:44:54 raspberrypi systemd[1]: mesh_bot.service: Control process exited, code=exited, status=1/FAILURE
Aug 10 23:44:54 raspberrypi systemd[1]: mesh_bot.service: Failed with result 'exit-code'.
Aug 10 23:44:54 raspberrypi systemd[1]: mesh_bot.service: Scheduled restart job, restart counter is at 4.
Aug 10 23:44:54 raspberrypi systemd[1]: Stopped mesh_bot.service - MESH-BOT.
Aug 10 23:44:54 raspberrypi systemd[1]: Started mesh_bot.service - MESH-BOT.
Aug 10 23:44:54 raspberrypi bash[7197]: Traceback (most recent call last):
Aug 10 23:44:54 raspberrypi bash[7197]:   File "/opt/meshing-around/mesh_bot.py", line 14, in <module>
Aug 10 23:44:54 raspberrypi bash[7197]:     from modules.log import *
Aug 10 23:44:54 raspberrypi bash[7197]:   File "/opt/meshing-around/modules/log.py", line 72, in <module>
Aug 10 23:44:54 raspberrypi bash[7197]:     file_handler_sys = TimedRotatingFileHandler('logs/meshbot.log', when='midnight', backupCount=log_backup_count, encoding='utf-8')
Aug 10 23:44:54 raspberrypi bash[7197]:                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Aug 10 23:44:54 raspberrypi bash[7197]:   File "/usr/lib/python3.11/logging/handlers.py", line 214, in __init__
Aug 10 23:44:54 raspberrypi bash[7197]:     BaseRotatingHandler.__init__(self, filename, 'a', encoding=encoding,
Aug 10 23:44:54 raspberrypi bash[7197]:   File "/usr/lib/python3.11/logging/handlers.py", line 58, in __init__
Aug 10 23:44:54 raspberrypi bash[7197]:     logging.FileHandler.__init__(self, filename, mode=mode,
Aug 10 23:44:54 raspberrypi bash[7197]:   File "/usr/lib/python3.11/logging/__init__.py", line 1181, in __init__
Aug 10 23:44:54 raspberrypi bash[7197]:     StreamHandler.__init__(self, self._open())
Aug 10 23:44:54 raspberrypi bash[7197]:                                  ^^^^^^^^^^^^
Aug 10 23:44:54 raspberrypi bash[7197]:   File "/usr/lib/python3.11/logging/__init__.py", line 1213, in _open
Aug 10 23:44:54 raspberrypi bash[7197]:     return open_func(self.baseFilename, self.mode,
Aug 10 23:44:54 raspberrypi bash[7197]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Aug 10 23:44:54 raspberrypi bash[7197]: PermissionError: [Errno 13] Permission denied: '/opt/meshing-around/logs/meshbot.log'
Aug 10 23:44:54 raspberrypi systemd[1]: mesh_bot.service: Control process exited, code=exited, status=1/FAILURE
Aug 10 23:44:54 raspberrypi systemd[1]: mesh_bot.service: Failed with result 'exit-code'.
Aug 10 23:44:55 raspberrypi systemd[1]: mesh_bot.service: Scheduled restart job, restart counter is at 5.
Aug 10 23:44:55 raspberrypi systemd[1]: Stopped mesh_bot.service - MESH-BOT.
Aug 10 23:44:55 raspberrypi systemd[1]: mesh_bot.service: Start request repeated too quickly.
Aug 10 23:44:55 raspberrypi systemd[1]: mesh_bot.service: Failed with result 'exit-code'.
Aug 10 23:44:55 raspberrypi systemd[1]: Failed to start mesh_bot.service - MESH-BOT.

To fix

$ sudo chown -R meshbot /opt/meshing-around/logs
$ sudo systemctl restart mesh_bot.service

To verify it's now running

$ sudo systemctl status mesh_bot.service
# or
$ sudo journalctl -u mesh_bot.service

@SpudGunMan : Does the chown need to change to meshbot:meshbot in install.sh: (I think it was owned by root?)
https://github.com/SpudGunMan/meshing-around/blob/2fc928139472461df1818ac123980dc69048f3ea/install.sh#L206-L207

Or perhaps running the bot directly as root created log files as root, and the user could no longer rotate the log?

I ran into the same/similar issue, and @SpudGunMan was [spot on](https://github.com/SpudGunMan/meshing-around/issues/168#issuecomment-3138329776). ## Issue ```bash $ sudo systemctl status mesh_bot.service × mesh_bot.service - MESH-BOT Loaded: loaded (/etc/systemd/system/mesh_bot.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Sun 2025-08-10 23:44:55 PDT; 8min ago Duration: 143ms Process: 7195 ExecStart=/usr/bin/bash launch.sh mesh (code=exited, status=0/SUCCESS) Process: 7198 ExecStop=pkill -f mesh_bot.py (code=exited, status=1/FAILURE) Main PID: 7195 (code=exited, status=0/SUCCESS) CPU: 126ms Aug 10 23:44:55 raspberrypi systemd[1]: mesh_bot.service: Scheduled restart job, restart counter is at 5. Aug 10 23:44:55 raspberrypi systemd[1]: Stopped mesh_bot.service - MESH-BOT. Aug 10 23:44:55 raspberrypi systemd[1]: mesh_bot.service: Start request repeated too quickly. Aug 10 23:44:55 raspberrypi systemd[1]: mesh_bot.service: Failed with result 'exit-code'. Aug 10 23:44:55 raspberrypi systemd[1]: Failed to start mesh_bot.service - MESH-BOT. ``` Running `journalctl` to see the stdout/stderr: ```bash $ sudo journalctl -u mesh_bot.service Aug 10 23:44:54 raspberrypi bash[7193]: PermissionError: [Errno 13] Permission denied: '/opt/meshing-around/logs/meshbot.log' Aug 10 23:44:54 raspberrypi systemd[1]: mesh_bot.service: Control process exited, code=exited, status=1/FAILURE Aug 10 23:44:54 raspberrypi systemd[1]: mesh_bot.service: Failed with result 'exit-code'. Aug 10 23:44:54 raspberrypi systemd[1]: mesh_bot.service: Scheduled restart job, restart counter is at 4. Aug 10 23:44:54 raspberrypi systemd[1]: Stopped mesh_bot.service - MESH-BOT. Aug 10 23:44:54 raspberrypi systemd[1]: Started mesh_bot.service - MESH-BOT. Aug 10 23:44:54 raspberrypi bash[7197]: Traceback (most recent call last): Aug 10 23:44:54 raspberrypi bash[7197]: File "/opt/meshing-around/mesh_bot.py", line 14, in <module> Aug 10 23:44:54 raspberrypi bash[7197]: from modules.log import * Aug 10 23:44:54 raspberrypi bash[7197]: File "/opt/meshing-around/modules/log.py", line 72, in <module> Aug 10 23:44:54 raspberrypi bash[7197]: file_handler_sys = TimedRotatingFileHandler('logs/meshbot.log', when='midnight', backupCount=log_backup_count, encoding='utf-8') Aug 10 23:44:54 raspberrypi bash[7197]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Aug 10 23:44:54 raspberrypi bash[7197]: File "/usr/lib/python3.11/logging/handlers.py", line 214, in __init__ Aug 10 23:44:54 raspberrypi bash[7197]: BaseRotatingHandler.__init__(self, filename, 'a', encoding=encoding, Aug 10 23:44:54 raspberrypi bash[7197]: File "/usr/lib/python3.11/logging/handlers.py", line 58, in __init__ Aug 10 23:44:54 raspberrypi bash[7197]: logging.FileHandler.__init__(self, filename, mode=mode, Aug 10 23:44:54 raspberrypi bash[7197]: File "/usr/lib/python3.11/logging/__init__.py", line 1181, in __init__ Aug 10 23:44:54 raspberrypi bash[7197]: StreamHandler.__init__(self, self._open()) Aug 10 23:44:54 raspberrypi bash[7197]: ^^^^^^^^^^^^ Aug 10 23:44:54 raspberrypi bash[7197]: File "/usr/lib/python3.11/logging/__init__.py", line 1213, in _open Aug 10 23:44:54 raspberrypi bash[7197]: return open_func(self.baseFilename, self.mode, Aug 10 23:44:54 raspberrypi bash[7197]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Aug 10 23:44:54 raspberrypi bash[7197]: PermissionError: [Errno 13] Permission denied: '/opt/meshing-around/logs/meshbot.log' Aug 10 23:44:54 raspberrypi systemd[1]: mesh_bot.service: Control process exited, code=exited, status=1/FAILURE Aug 10 23:44:54 raspberrypi systemd[1]: mesh_bot.service: Failed with result 'exit-code'. Aug 10 23:44:55 raspberrypi systemd[1]: mesh_bot.service: Scheduled restart job, restart counter is at 5. Aug 10 23:44:55 raspberrypi systemd[1]: Stopped mesh_bot.service - MESH-BOT. Aug 10 23:44:55 raspberrypi systemd[1]: mesh_bot.service: Start request repeated too quickly. Aug 10 23:44:55 raspberrypi systemd[1]: mesh_bot.service: Failed with result 'exit-code'. Aug 10 23:44:55 raspberrypi systemd[1]: Failed to start mesh_bot.service - MESH-BOT. ``` ## To fix ```bash $ sudo chown -R meshbot /opt/meshing-around/logs $ sudo systemctl restart mesh_bot.service ``` ### To verify it's now running ```bash $ sudo systemctl status mesh_bot.service # or $ sudo journalctl -u mesh_bot.service ``` --- @SpudGunMan : Does the chown need to change to `meshbot:meshbot` in install.sh: (I think it was owned by `root`?) https://github.com/SpudGunMan/meshing-around/blob/2fc928139472461df1818ac123980dc69048f3ea/install.sh#L206-L207 Or perhaps running the bot directly as `root` created log files as `root`, and the user could no longer rotate the log? <!-- github-comment-id:3173521237 -->
adam commented 2026-10-05 01:19:05 +02:00
Author
Owner
Copy link
Copy source

$whoami is either meshbot or the local current user depending on the install choice.

$whoami is either meshbot or the local current user depending on the install choice. <!-- github-comment-id:3181386880 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/meshing-around#65