perfSONAR User Q&A and Other Discussion

[Muhammad Akhdhor <>]

Hello,

After doing some debugging, it seems to me that supervisord expects the owampd and twampd processes to run in the foreground. Since they're started in the background and an exit code of 0 is returned for each, supervisord tries to restart them and eventually "FATAL state" is reported for those two processes.

Would it be possible to add the "-Z" option to the command lines in /etc/supervisord.conf in the container image so that those FATAL state errors are resolved? Those processes in supervisord.conf would be defined as:

[program:owampd]

chown=owamp:owamp

command=/usr/bin/owampd -c /etc/owamp-server -R /var/run -Z

[program:twampd]

chown=twamp:twamp

command=/usr/bin/twampd -c /etc/twamp-server -R /var/run -Z

Thanks,

Muhammad 

On Wed, May 24, 2023 at 7:21 PM Muhammad Akhdhor <> wrote:

Hello,

I'm trying the latest perfSONAR v5 image with docker but I see some error messages for two daemons as you can see below:

[root@dev-env ~]# docker run --net=host perfsonar/testpoint:v5.0.1

2023-05-24 23:11:25,522 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.

2023-05-24 23:11:25,525 INFO supervisord started with pid 1

2023-05-24 23:11:26,527 INFO spawned: 'httpd' with pid 9

2023-05-24 23:11:26,529 INFO spawned: 'pscheduler-ticker' with pid 10

2023-05-24 23:11:26,530 INFO spawned: 'postgresql' with pid 11

2023-05-24 23:11:26,531 INFO spawned: 'twampd' with pid 12

2023-05-24 23:11:26,533 INFO spawned: 'ls_registration_daemon' with pid 13

2023-05-24 23:11:26,535 INFO spawned: 'pscheduler-scheduler' with pid 14

2023-05-24 23:11:26,537 INFO spawned: 'pscheduler-archiver' with pid 15

2023-05-24 23:11:26,538 INFO spawned: 'owampd' with pid 16

2023-05-24 23:11:26,540 INFO spawned: 'rsyslog' with pid 17

2023-05-24 23:11:26,572 INFO spawned: 'psconfig_pscheduler_agent' with pid 18

2023-05-24 23:11:26,574 INFO spawned: 'pscheduler-runner' with pid 23

2023-05-24 23:11:26,575 INFO exited: twampd (exit status 0; not expected)

2023-05-24 23:11:26,575 INFO exited: owampd (exit status 0; not expected)

2023-05-24 23:11:27,601 INFO success: httpd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2023-05-24 23:11:27,601 INFO success: pscheduler-ticker entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2023-05-24 23:11:27,601 INFO success: postgresql entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2023-05-24 23:11:27,602 INFO spawned: 'twampd' with pid 232

2023-05-24 23:11:27,602 INFO success: ls_registration_daemon entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2023-05-24 23:11:27,602 INFO success: pscheduler-scheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2023-05-24 23:11:27,602 INFO success: pscheduler-archiver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2023-05-24 23:11:27,604 INFO spawned: 'owampd' with pid 233

2023-05-24 23:11:27,604 INFO success: rsyslog entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2023-05-24 23:11:27,604 INFO success: psconfig_pscheduler_agent entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2023-05-24 23:11:27,604 INFO success: pscheduler-runner entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2023-05-24 23:11:27,623 INFO exited: twampd (exit status 0; not expected)

2023-05-24 23:11:27,634 INFO exited: psconfig_pscheduler_agent (exit status 0; expected)

2023-05-24 23:11:27,634 INFO exited: owampd (exit status 0; not expected)

2023-05-24 23:11:27,635 INFO reaped unknown pid 235

2023-05-24 23:11:27,636 INFO reaped unknown pid 237

2023-05-24 23:11:27,792 INFO exited: ls_registration_daemon (exit status 0; expected)

2023-05-24 23:11:29,795 INFO spawned: 'twampd' with pid 355

2023-05-24 23:11:29,796 INFO spawned: 'owampd' with pid 356

2023-05-24 23:11:29,804 INFO exited: twampd (exit status 0; not expected)

2023-05-24 23:11:29,804 INFO exited: owampd (exit status 0; not expected)

2023-05-24 23:11:29,804 INFO reaped unknown pid 357

2023-05-24 23:11:29,805 INFO reaped unknown pid 358

2023-05-24 23:11:32,809 INFO spawned: 'twampd' with pid 361

2023-05-24 23:11:32,810 INFO spawned: 'owampd' with pid 362

2023-05-24 23:11:32,816 INFO exited: twampd (exit status 0; not expected)

2023-05-24 23:11:32,816 INFO gave up: twampd entered FATAL state, too many start retries too quickly

2023-05-24 23:11:32,816 INFO exited: owampd (exit status 0; not expected)

2023-05-24 23:11:32,816 INFO reaped unknown pid 363

2023-05-24 23:11:32,817 INFO gave up: owampd entered FATAL state, too many start retries too quickly

2023-05-24 23:11:32,817 INFO reaped unknown pid 364

I'm specifically looking at twampd and owampd errors. Are they expected? Do I need some additional configuration to resolve those problems? 

Thanks,

Muhammad