Nethvoice - modules watcher, reports-scheduler and phonebook-update not starting automatically

NethServer Version: NS8
Module: Nethvoice

Modules in Nethvoice not starting and I don’t know why.

What would cause this and how would I fix it.

Jeff

1 Like

I can confirm, I have the exact same issues

reports-scheduler is marked as failed.

I think “reports-scheduler.service” is run daily by a timer “reports-scheduler.timer” (not always active).

Check nethvoice’s log for clues, or get more info by checking the status of the services or through journalctl…

Haven’t checked it but maybe the systemctl command is like this:

runagent -m nethvoice3 systemctl status -l --user reports-scheduler.*

phonebook-update is also run by a timer. Not sure, but is it possible that the service needs to be enabled even if inactive until triggered by the timer.

reports-scheduler.timer - Scheduler that handles reports generation

Loaded: loaded (/home/nethvoice2/.config/systemd/user/reports-scheduler.timer; enabled; preset: disabled)

Active: active (waiting) since Sun 2024-09-22 03:51:33 CEST; 1 week 6 days ago

Until: Sun 2024-09-22 03:51:33 CEST; 1 week 6 days ago

Trigger: Sun 2024-10-06 00:00:00 CEST; 9h left

Triggers: reports-scheduler.service

Warning: some journal files were not opened due to insufficient permissions.

× reports-scheduler.service - Generate reports

Loaded: loaded (/home/nethvoice2/.config/systemd/user/reports-scheduler.service; static)

Active: failed (Result: exit-code) since Sat 2024-10-05 00:00:29 CEST; 14h ago

TriggeredBy: reports-scheduler.timer

Process: 2726547 ExecStart=/usr/bin/podman exec freepbx /opt/nethvoice-report/scripts/queue-miner.php (code=exited, status=0/SUCCESS)

Process: 2726635 ExecStart=/usr/bin/podman exec reports-api tasks cdr (code=exited, status=0/SUCCESS)

Process: 2726684 ExecStart=/usr/bin/podman exec reports-api tasks cost (code=exited, status=0/SUCCESS)

Process: 2726715 ExecStart=/usr/bin/podman exec reports-api tasks views (code=exited, status=0/SUCCESS)

Process: 2726886 ExecStart=/usr/bin/podman exec reports-api tasks queries (code=exited, status=1/FAILURE)

Main PID: 2726886 (code=exited, status=1/FAILURE)

CPU: 1.044s

Oct 05 00:00:20 srv01 podman[2726684]: 2024-10-05 00:00:20.887195305 +0200 CEST m=+0.147235154 container exec_died 788a040e0682827811beb81f8835e31e3d10e13dbe1b0e8b43d9afe728c9b594 (image=ghcr.io/nethesis/n>

Oct 05 00:00:21 srv01 podman[2726715]: 2024-10-05 00:00:21.034900493 +0200 CEST m=+0.098882605 container exec 788a040e0682827811beb81f8835e31e3d10e13dbe1b0e8b43d9afe728c9b594 (image=ghcr.io/nethesis/nethvo>

Oct 05 00:00:28 srv01 podman[2726715]: 2024-10-05 00:00:28.884958429 +0200 CEST m=+7.948940541 container exec_died 788a040e0682827811beb81f8835e31e3d10e13dbe1b0e8b43d9afe728c9b594 (image=ghcr.io/nethesis/n>

Oct 05 00:00:29 srv01 podman[2726886]: 2024-10-05 00:00:29.043413604 +0200 CEST m=+0.103909299 container exec 788a040e0682827811beb81f8835e31e3d10e13dbe1b0e8b43d9afe728c9b594 (image=ghcr.io/nethesis/nethvo>

Oct 05 00:00:29 srv01 podman[2726886]: [ERROR]: FATAL: Login error, [STATUS]: 401

Oct 05 00:00:29 srv01 podman[2726886]: 2024-10-05 00:00:29.092540656 +0200 CEST m=+0.153036351 container exec_died 788a040e0682827811beb81f8835e31e3d10e13dbe1b0e8b43d9afe728c9b594 (image=ghcr.io/nethesis/n>

Oct 05 00:00:29 srv01 systemd[1507]: reports-scheduler.service: Main process exited, code=exited, status=1/FAILURE

Oct 05 00:00:29 srv01 systemd[1507]: reports-scheduler.service: Failed with result ‘exit-code’.

Oct 05 00:00:29 srv01 systemd[1507]: Failed to start Generate reports.

Oct 05 00:00:29 srv01 systemd[1507]: reports-scheduler.service: Consumed 1.044s CPU time.

Here is what I got -