perfsonar-user - Re: [perfsonar-user] pscheduler-ticker.service constantly in 'activating' mode
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Antoine Delvaux <>
- To: Prannoy Sablok <>
- Cc: perfsonar-user <>
- Subject: Re: [perfsonar-user] pscheduler-ticker.service constantly in 'activating' mode
- Date: Fri, 30 Jul 2021 11:23:27 +0100
Hi Prannoy,
Is it the same machine where you had the iperf3 issue previously? Or is it a machine that was running fine before? Or is it a new clean install?
Antoine.
Le 30 juil. 2021 à 04:18, Prannoy Sablok <> a écrit :Hi Antoine ,Below is the result from pscheduler version -pscheduler-account 4.3.4-1pscheduler-archiver-bitbucket 4.3.4-1pscheduler-archiver-esmond 4.3.4-1pscheduler-archiver-failer 4.3.4-1pscheduler-archiver-http 4.3.4-1pscheduler-archiver-kafka 4.3.4-1pscheduler-archiver-rabbitmq 4.3.4-1pscheduler-archiver-syslog 4.3.4-1pscheduler-bundle-full 4.3.4-1pscheduler-bundle-full-nos3pscheduler-context-changefail 4.3.4-1pscheduler-context-changenothing 4.3.4-1pscheduler-context-linuxnns 4.3.4-1pscheduler-context-linuxvrf 4.3.4-1pscheduler-core 4.3.4-1pscheduler-docs 4.3.4-1pscheduler-jq-library 4.3.4-1pscheduler-server 4.3.4-1pscheduler-test-clock 4.3.4-1pscheduler-test-disk-to-disk 4.3.4-1pscheduler-test-dns 4.3.4-1pscheduler-test-http 4.3.4-1pscheduler-test-idle 4.3.4-1pscheduler-test-idlebgm 4.3.4-1pscheduler-test-idleex 4.3.4-1pscheduler-test-latency 4.3.4-1pscheduler-test-latencybg 4.3.4-1pscheduler-test-rtt 4.3.4-1pscheduler-test-s3throughput 4.3.4-1pscheduler-test-simplestream 4.3.4-1pscheduler-test-throughput 4.3.4-1pscheduler-test-trace 4.3.4-1pscheduler-tool-curl 4.3.4-1pscheduler-tool-dnspy 4.3.4-1pscheduler-tool-ethr 4.3.4-1pscheduler-tool-iperf2 4.3.4-1pscheduler-tool-iperf3 4.3.4-1pscheduler-tool-nuttcp 4.3.4-1pscheduler-tool-owping 4.3.4-1pscheduler-tool-paris-traceroute 4.3.4-1pscheduler-tool-ping 4.3.4-1pscheduler-tool-powstream 4.3.4-1pscheduler-tool-psclock 4.3.4-1pscheduler-tool-psurl 4.3.4-1pscheduler-tool-s3-benchmark 4.3.4-1pscheduler-tool-simplestreamer 4.3.4-1pscheduler-tool-sleep 4.3.4-1pscheduler-tool-sleepbgm 4.3.4-1pscheduler-tool-snooze 4.3.4-1pscheduler-tool-tracepath 4.3.4-1pscheduler-tool-traceroute 4.3.4-1pscheduler-tool-twping 4.3.4-1The OS is Ubuntu 18.04.5 LTS.Kind Regards,Prannoy SABLOK
Technical Specialist
Singapore Advanced Research and Education Network (SingAREN)
M +65 87492366| E
www.singaren.net.sg--On Thu, 29 Jul 2021 at 23:19, Antoine Delvaux <> wrote:Hi Prannoy,Can you please tell us which version of perfSONAR that is and what is the OS running on this system?Thanks,Antoine.Le 29 juil. 2021 à 06:58, Prannoy Sablok <> a écrit :Hi all,<image001.jpg>--I have been trying to run a pscheduler task on a server but it keeps throwing the following error -~$ pscheduler task throughput dtn.singaren.net.sgCould not find test throughput on serverThis occurs with all pscheduler tasks. I checked service status and there seems to be a problem with the ticker service, as below -~$ systemctl status pscheduler-ticker.service● pscheduler-ticker.service - pScheduler server - tickerLoaded: loaded (/lib/systemd/system/pscheduler-ticker.service; enabled; vendor preset: enabled)Active: activating (auto-restart) (Result: exit-code) since Thu 2021-07-29 00:43:44 CDT; 679ms agoProcess: 27223 ExecStopPost=/bin/rm -rf /var/run/pscheduler-server/ticker (code=exited, status=0/SUCCESS)Process: 27187 ExecStart=/usr/lib/pscheduler/daemons/ticker --daemon --pid-file /var/run/pscheduler-server/ticker/pid --dsn @/etProcess: 27178 ExecStartPre=/bin/sh -c if [ -r /etc/pscheduler/daemons/ticker.conf ]; then opts=$(sed -e 's/#.*$//' /etc/pscheduProcess: 27177 ExecStartPre=/bin/mv /var/run/pscheduler-server/ticker/pid.build /var/run/pscheduler-server/ticker/pid (code=exitProcess: 27176 ExecStartPre=/bin/chown pscheduler:pscheduler /var/run/pscheduler-server/ticker/pid.build (code=exited, status=0/Process: 27175 ExecStartPre=/usr/bin/touch -f /var/run/pscheduler-server/ticker/pid.build (code=exited, status=0/SUCCESS)Process: 27174 ExecStartPre=/bin/rm -f /var/run/pscheduler-server/ticker/pid.build (code=exited, status=0/SUCCESS)Process: 27173 ExecStartPre=/bin/chown pscheduler:pscheduler /var/run/pscheduler-server/ticker/tmp (code=exited, status=0/SUCCESProcess: 27172 ExecStartPre=/bin/chmod 700 /var/run/pscheduler-server/ticker/tmp (code=exited, status=0/SUCCESS)Process: 27171 ExecStartPre=/bin/mkdir -p /var/run/pscheduler-server/ticker/tmp (code=exited, status=0/SUCCESS)Process: 27170 ExecStartPre=/bin/chmod 755 /var/run/pscheduler-server/ticker (code=exited, status=0/SUCCESS)Process: 27166 ExecStartPre=/bin/chown pscheduler:pscheduler /var/run/pscheduler-server/ticker (code=exited, status=0/SUCCESS)Process: 27158 ExecStartPre=/bin/mkdir -p /var/run/pscheduler-server/ticker (code=exited, status=0/SUCCESS)Main PID: 27187 (code=exited, status=1/FAILURE)Upon further inspecting the pscheduler.log I found the following -$ tail -n 20 pscheduler.logJul 28 13:02:39 dtn098 safe_run/ticker ERROR Traceback (most recent call last):Jul 28 13:02:39 dtn098 safe_run/ticker ERROR File "/usr/lib/python3/dist-packages/pscheduler/saferun.py", line 76, in safe_runJul 28 13:02:39 dtn098 safe_run/ticker ERROR function()Jul 28 13:02:39 dtn098 safe_run/ticker ERROR File "/usr/lib/pscheduler/daemons/ticker", line 170, in <lambda>Jul 28 13:02:39 dtn098 safe_run/ticker ERROR pscheduler.safe_run(lambda: main_program())Jul 28 13:02:39 dtn098 safe_run/ticker ERROR File "/usr/lib/pscheduler/daemons/ticker", line 132, in main_programJul 28 13:02:39 dtn098 safe_run/ticker ERROR cursor.execute("SELECT cold_boot()")Jul 28 13:02:39 dtn098 safe_run/ticker ERROR psycopg2.InternalError: AttributeError: module 'jsonschema' has no attribute 'Draft7Validator'Jul 28 13:02:39 dtn098 safe_run/ticker ERROR CONTEXT: Traceback (most recent call last):Jul 28 13:02:39 dtn098 safe_run/ticker ERROR PL/Python function "json_validate", line 17, in <module>Jul 28 13:02:39 dtn098 safe_run/ticker ERROR "required": [ "" ]Jul 28 13:02:39 dtn098 safe_run/ticker ERROR PL/Python function "json_validate", line 1411, in json_validateJul 28 13:02:39 dtn098 safe_run/ticker ERROR PL/Python function "json_validate"Jul 28 13:02:39 dtn098 safe_run/ticker ERROR PL/pgSQL function test_boot() line 35 at assignmentJul 28 13:02:39 dtn098 safe_run/ticker ERROR SQL statement "SELECT test_boot()"Jul 28 13:02:39 dtn098 safe_run/ticker ERROR PL/pgSQL function warm_boot() line 4 at PERFORMJul 28 13:02:39 dtn098 safe_run/ticker ERROR SQL statement "SELECT warm_boot()"Jul 28 13:02:39 dtn098 safe_run/ticker ERROR PL/pgSQL function cold_boot() line 4 at PERFORMJul 28 13:02:39 dtn098 safe_run/ticker ERROR Waiting 0.25 seconds before restartingJul 28 13:02:39 dtn098 safe_run/ticker ERROR Restarting: ['/usr/lib/pscheduler/daemons/ticker', '--daemon', '--pid-file', '/var/run/pscheduler-server/ticker/pid', '--dsn', '@/etc/pscheduler/database/database-dsn']It seems like there's an issue with a python dependency. Would the best way to fix this be to upgrade the jsonschema module with "pip install --upgrade jsonschema" or something else?Kind Regards,Prannoy SABLOK
Technical Specialist
Singapore Advanced Research and Education Network (SingAREN)
M +65 87492366| E
www.singaren.net.sg
To unsubscribe from this list: https://lists.internet2.edu/sympa/signoff/perfsonar-user
To unsubscribe from this list: https://lists.internet2.edu/sympa/signoff/perfsonar-user
- [perfsonar-user] pscheduler-ticker.service constantly in 'activating' mode, Prannoy Sablok, 07/29/2021
- Re: [perfsonar-user] pscheduler-ticker.service constantly in 'activating' mode, Antoine Delvaux, 07/29/2021
- Re: [perfsonar-user] pscheduler-ticker.service constantly in 'activating' mode, Prannoy Sablok, 07/30/2021
- Re: [perfsonar-user] pscheduler-ticker.service constantly in 'activating' mode, Antoine Delvaux, 07/30/2021
- Re: [perfsonar-user] pscheduler-ticker.service constantly in 'activating' mode, Prannoy Sablok, 07/30/2021
- Re: [perfsonar-user] pscheduler-ticker.service constantly in 'activating' mode, Antoine Delvaux, 07/29/2021
Archive powered by MHonArc 2.6.24.