the instance become not longer accessible via ssh.
The last log reports
Jun 1 20:11:59 test esmith::event[2221]: Action: /etc/e-smith/events/runlevel-adjust/S95create-default-accounts SUCCESS [0.079828]
Jun 1 20:11:59 test esmith::event[2221]: Event: runlevel-adjust SUCCESS
Jun 1 20:11:59 test esmith::event[1787]: Action: /etc/e-smith/events/system-init/S90system-adjust SUCCESS [15.659357]
Jun 1 20:11:59 test esmith::event[2341]: Event: interface-update
There is someone know what command performs interface-update event and if this to something to firewall rules or change ssh port?
The instance of the virtual machine after this remain unreachable also after a reset (reboot).
had a similar problem when I did the same on my personal server (hosted on a VPS)
AFAIR, during that event, the ipv4 stops working (ipv6 keeps working)
I remember a post of mine on Nethesis italia facebook group
I’ve console access until in /var/log/message appear the log about the event interface-update
After this I must reinitialize a new istance of CentOS (fortunately it does not take much).
If you want, I can create a new instance of CentOS and than performe a new Nethserver Instalation over it, the best should be doing it with a more verbose log. There is an option to do this?
I’m wathing also /var/log/nethserver-install.log who is just the standard output of the command
Edit the nethserver-install to skip the command on line 104
logexec "/sbin/e-smith/signal-event system-init"
Run nethserver-install, remove the symlink and finally run signal-event system-init.
Anyway (thanks to @giacomo) you’ll probably hit a routing problem due to mask 255.255.255.255, which is not configured correctly, thus the VPS becomes unreachable the first time interface-update is executed.
You could create /sbin/ifup-local executable script that fixes the routing table each time an interface is ifup-ed. See /etc/sysconfig/network-scripts/ifup-post for details.
The GATEWAY setting in ifcfg-eth* must point an IP in the same subnet. Now you have a single IP subnet, so it does not work. The solution would be setting up a static route, but /etc/sysconfig/network-scripts/route-* is overwritten by interface-update event.
Thus, as last resort, /sbin/ifup-local seemed viable to me…
Mission completed… soon a report of the steps needed to run a NetServer instance on Google Compute Engine.
Just one impression. Google Compute Engine management interface is more clean than the one of Amazon EC2… but NethServer installation on it is a little more tricky…