-
Notifications
You must be signed in to change notification settings - Fork 35
Open
Description
I have a strange problem on a clean quantum mobile machine.
Executing the command (aiida) max@qmobile:~$ systemctl --type=service shows that AiiDA daemon is still activating
UNIT LOAD ACTIVE SUB DESCRIPTION
[email protected] loaded activating auto-restart AiiDA daemon service
verdi status shows that the daemon is not running:
(aiida) max@qmobile:~$ verdi status
✔ config dir: /home/max/.aiida
✔ profile: On profile generic
✔ repository: /home/max/.aiida/repository/generic
✔ postgres: Connected as aiida@localhost:5432
✔ rabbitmq: Connected as amqp://guest:[email protected]:5672?heartbeat=600
⏺ daemon: The daemon is not running
starting the daemon fails
(aiida) max@qmobile:~$ verdi daemon start
Starting the daemon... FAILED
Try to run 'verdi daemon start --foreground' to potentially see the exception
(aiida) max@qmobile:~$ verdi daemon start --foreground
Starting the daemon... FAILED
Critical: Command '['verdi', '-p', 'generic', 'daemon', 'start-circus', '--foreground', '1']' returned non-zero exit status 1.
The daemon is now running even though it fails to start !!
(aiida) max@qmobile:~$ verdi status
✔ config dir: /home/max/.aiida
✔ profile: On profile generic
✔ repository: /home/max/.aiida/repository/generic
✔ postgres: Connected as aiida@localhost:5432
✔ rabbitmq: Connected as amqp://guest:[email protected]:5672?heartbeat=600
✔ daemon: Daemon is running as PID 4602 since 2021-07-31 07:27:05
AiiDA daemon is still activating...
(aiida) max@qmobile:~$ systemctl --type=service
UNIT LOAD ACTIVE SUB DESCRIPTION
[email protected] loaded activating auto-restart AiiDA daemon service
Metadata
Metadata
Assignees
Labels
No labels