restart after binding directories

[kexinliu0001]

hi,

I bindedd directories as installation step 5 to make files visible to PYP.
but when I tried to restart, it failed.

how can I overcome it?

thx!!

systemctl restart nextPYP:

systemctl status nextPYP.service:

I also tried "journalctl -u nextPYP" as in troubleshooting:

[abartesaghi]

We can't see the attachments, can you upload the files again?

[kexinliu0001]

thank you for reminding！I've updated again.

and I also tried not binding directories (without "binds = []" in confit.toml), but the it still cannot be restarted.

I tried to reinstall nextPYP, but it still not work

PYP_USER=nextpyp ./install

[abartesaghi]

As suggested in the installation docs, do you see any error messages in the logs (specifically the micromon one)?

[kexinliu0001]

hello, I met the same problem today.

I found that I cannot connect the localhost website, and tried to restart, and failed.
the logs in the micromon is:


and the latest update in the logs ([2024-01-09 14:07:55,676]) is 8 hours ago. I'm not sure if it's useful to know why nextpyp cannot be restarted now.
I tried to restart again, there is no error message updated in the micromon logs.

when systemctl status nextpyp:

it seemed to keep activating but cannot be activated and started successfully.
when journalctl -xe:

[cuchaz]

The relevant error message seems to be here:

A host processor is already running. Stop it before starting Micromon.
And then delete the files /tmp/micromon.hostprocessor.pid and /tmp/micromon.hostprocessor.pipe

Have you tried doing that and then restarting?

[kexinliu0001]

sorry, I still cannot find the error message you cited in the logs 😭

and do you mean it might be useful if:

systemctl stop nextPYP
delete the files in /tmp/micromon.hostprocessor.pid and /tmp/micromon.hostprocessor.pipe
and then
systemctl start nextPYP
?

[cuchaz]

If it helps, here's the error message you shared that I'm referring to:

Yes, try a small script like this:

sudo systemctl stop nextPYP
rm /tmp/micromon.hostprocessor.pid
rm /tmp/micromon.hostprocessor.pipe
sudo systemctl start nextPYP

Sometimes the shutdown process doesn't perform cleanup correctly and the next time the service is started, it looks like an old service is still running. That's where that error message comes from. If you know another service isn't actually running, then it's safe to do the cleanup manually (ie, delete the files) and then restart the service.

This seems to be a common problem with other people too, so we'll look into better ways to handle startup and shutdown. Thanks for reporting the issue!

[kexinliu0001]

Thank you! It really helps! 😄