Automatic reboot problem in console mode

1

I replaced my miniPC by a model with the same configuration but an N100 processor.
I installed the Core 193 version directly in console mode and restored the backup
Everything works fine except that I have a scheduled reboot in the morning at 4:30 a.m., which no longer works.

When I plug in the console with Putty, the reboot start normally

Any ideas?

2

It seems to be a problem with the RJ45/USB adapter cable extension (I moved my MiniPC and extended it with an RJ45 cable).

  • If I leave the adapter plugged directly into the RJ45 side of the miniPC and unplugged or plugged into the USB side powered or not (PC on or off): boot works.
  • If I plug the RJ45 extension cable into the miniPC and the adapter at the end of the extension cable plugged into the USB side and powered (PC on): boot works.
  • If I plug the RJ45 extension cable into the miniPC and the adapter at the end of the extension cable unplugged or plugged into the USB side but not powered (PC off): boot remains stuck.
    In this case, I have to turn on the PC and launch Putty for booting to restart.
3

Change your chron job to this command:

/sbin/shutdown -r now

because the reboot command waits for all except the user to be off and it might interpret the serial console as a separate session depending on how the serial console is set up.

That is the only thing I can think of. Besides it works better with the full path in most distros and chron prefers this command being an entry instead of a remote call from a script.

4

Thanks for the idea, but this is that command that IPFire launches when you schedule a reboot.
https://ipfire:444/cgi-bin/connscheduler.cgi

/usr/local/bin/ipfirereboot

Actually, it’s the boot that’s blocked regardless of how you shutdown or reboot.

5

I don’t even have that page (connscheduler.cgi) .

But I would just insert a crontab entry in /var/spool/cron/root.orig

Since that is the crontab for the system.

But any software that calls shutdown has to have root authority as it has to be executed by root to disconnect all sessions and restart.

6

Capture d'Ă©cran 2025-04-22 161907
Capture d'Ă©cran 2025-04-22 161907596Ă—437 23.1 KB

Capture d'Ă©cran 2025-04-22 162248
Capture d'Ă©cran 2025-04-22 1622481229Ă—935 45.1 KB

I tested it with the PC’s native COM port, and it’s worse.
I think it’s simply a problem with the RJ45 cable length.
RS232 doesn’t work properly over RJ45 cabling.

I disabled the reboot :wink:

1 Like
7

Oh ok, But I would still do a chron entry manually.

But this is something to raise a bug on since its not executing shutdown properly. As it should call the command directly and executed by a root-group program as root.