-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Systemd: gandi-postboot startup error #5
Comments
Hi, The "useless" script is the default we use when we did not provision an init script on the node. Were you testing this on our new datacenter ? Also, the postboot script should not assume it'll be provided with a python script, we should probably fix that. |
Hello ! The server with these scripts has been created 2 or 3 years ago and is located at Bissen. I assume it uses the GandiV4 platform. |
While debugging #6, i noticed this same problem:
|
Still seeing this problem any my Debian 9 system. Also seems to affect bootstrap.d/01-config_swap which also assumes /gandi/init is a python script if it is executable. |
Still seeing the same problem on my Debian 11 system. root@auckland:~# dpkg --list | grep gandi
ii gandi-hosting-vm2 2.41 all scripts for virtual machine on Gandi IaaS BTW I get a lot of other errors (notably on root@auckland:~# journalctl -b -0 | grep gandi
Jan 03 09:21:47 auckland systemd[1]: /usr/share/gandi/systemd/gandi-postboot.service:15: Support for option SysVStartPriority= has been removed and it is ignored
Jan 03 09:21:47 auckland systemd-udevd[494]: /etc/udev/rules.d/86-gandi.rules:14 Invalid value for OPTIONS key, ignoring: 'last_rule'
Jan 03 09:21:47 auckland systemd-udevd[494]: /etc/udev/rules.d/86-gandi.rules:15 Invalid value for OPTIONS key, ignoring: 'last_rule'
Jan 03 09:21:47 auckland systemd-udevd[494]: /etc/udev/rules.d/86-gandi.rules:16 Invalid value for OPTIONS key, ignoring: 'ignore_device'
Jan 03 09:21:47 auckland systemd-udevd[494]: /etc/udev/rules.d/86-gandi.rules:16 The line takes no effect, ignoring.
Jan 03 09:21:47 auckland systemd-udevd[494]: /etc/udev/rules.d/86-gandi.rules:22 Invalid value for OPTIONS key, ignoring: 'last_rule'
Jan 03 09:21:47 auckland systemd-udevd[494]: /etc/udev/rules.d/86-gandi.rules:32 Invalid value for OPTIONS key, ignoring: 'last_rule'
Jan 03 09:21:48 auckland gandi[562]: /dev/xvda1 / sys-auckland is now available
Jan 03 09:21:48 auckland gandi[560]: /dev/xvdd / donnees03 is now available
Jan 03 09:21:48 auckland gandi[564]: /dev/xvdb / donnees02 is now available
Jan 03 09:21:48 auckland gandi[558]: /dev/xvda2 / is now available
Jan 03 09:21:49 auckland gandi[650]:
Jan 03 09:21:49 auckland gandi[654]:
Jan 03 09:21:50 auckland gandi[712]: Cannot find tarball and info in the swap space. Continue formatting.
Jan 03 09:21:50 auckland gandi-bootstrap[688]: Cannot find tarball and info in the swap space. Continue formatting.
Jan 03 09:21:51 auckland gandi[822]:
Jan 03 09:21:51 auckland gandi[856]: 01-config_swap executed correctly.
Jan 03 09:21:51 auckland gandi[863]: 02-config_sysctl executed correctly.
Jan 03 09:21:51 auckland gandi[870]: resize2fs 1.46.2 (28-Feb-2021)
Jan 03 09:21:51 auckland gandi[870]: The filesystem is already 2621440 (4k) blocks long. Nothing to do!
Jan 03 09:21:51 auckland gandi[870]:
Jan 03 09:21:51 auckland gandi[874]: 03-resize_main_disk executed correctly.
Jan 03 09:21:51 auckland systemd[1]: gandi-bootstrap.service: Succeeded.
Jan 03 09:21:51 auckland gandi[881]:
Jan 03 09:21:52 auckland gandi[908]: 01-config_console executed correctly.
Jan 03 09:21:52 auckland gandi-config[913]: awk: cmd. line:1: warning: escape sequence `\s' treated as plain `s'
Jan 03 09:21:52 auckland gandi[919]: 02-config_system_file executed correctly.
Jan 03 09:21:52 auckland gandi[932]: 03-vm-fix-cron executed correctly.
Jan 03 09:21:52 auckland gandi[941]: 07-config_timezone executed correctly.
Jan 03 09:21:52 auckland gandi[949]: 11-config_ssh executed correctly.
Jan 03 09:21:52 auckland gandi[958]: 13-config_motd executed correctly.
Jan 03 09:21:52 auckland gandi[977]: 16-vm-fix-ext3 executed correctly.
Jan 03 09:21:52 auckland systemd[1]: gandi-config.service: Succeeded.
Jan 03 09:21:52 auckland gandi[1006]:
Jan 03 09:21:52 auckland gandi[1011]:
Jan 03 09:21:52 auckland gandi[1013]:
Jan 03 09:21:52 auckland gandi[1021]:
Jan 03 09:21:52 auckland gandi-mount[980]: Starting gandi-mount: ok.
Jan 03 09:21:52 auckland systemd[1]: gandi-mount.service: Succeeded.
Jan 03 09:21:53 auckland gandi-postboot[1014]: File "/gandi/init", line 3
Jan 03 09:21:53 auckland gandi-postboot[1014]: echo "I'm a useless script most of the times"
Jan 03 09:21:53 auckland gandi-postboot[1014]: ^
Jan 03 09:21:53 auckland gandi-postboot[1014]: SyntaxError: invalid syntax
Jan 03 09:21:53 auckland systemd[1]: gandi-postboot.service: Main process exited, code=exited, status=1/FAILURE
Jan 03 09:21:53 auckland systemd[1]: gandi-postboot.service: Failed with result 'exit-code'. |
Hi,
Currently, gandi-postboot init script run
/usr/bin/python2 /gandi/init
at startup (or/usr/bin/python
if python2 doesn't exists).On my server, the script
/gandi/init
contains exactly this code:Obviously, it's a Shell script, so its execution by Python interpreter is not possible. As a result, the systemd unit "gandi-postboot" don't run and the service remains in "failed" state:
I'm on Debian 8 with kernel 3.12.70:
Gandi-hosting-vm2 is installed, version 2.6
The text was updated successfully, but these errors were encountered: