OpenVZ Forum


Home » General » Discussions » OpenVZ isn't pingable after reboot (Have rebooted my container and it doesn't work anymore)
OpenVZ isn't pingable after reboot [message #52012] Fri, 24 April 2015 07:15 Go to next message
blognn is currently offline  blognn
Messages: 1
Registered: April 2015
Junior Member
From: *132.101.197.dynamic.adsl.gvt.net.br
Hi

I think I messed up with a container. I thought it had been compromissed and copied a sshd file into the container when it was stopped. After starting it doesn't work anymore. I need someone to fix it.

On the host it shows:
Container is mounted
Adding IP address(es): ...
/bin/cp: cannot stat `ifcfg-venet0:*': No such file or directory
ERROR: Unable to backup interface config files

On the container it shows (replace domain name for 'mydomain':
/vz/private/120/var/log/messages
Apr 24 03:34:18 mydomain syslogd 1.4.1: restart.
Apr 24 03:34:19 mydomain kernel: klogd 1.4.1, log source = /proc/kmsg started.
Apr 24 03:34:19 mydomain iscsid: iSCSI logger with pid=1354 started!
Apr 24 03:34:19 mydomain iscsid: Missing or Invalid version from /sys/module/scsi_transport_iscsi/version. Make sure a up to date scsi_transport_iscsi module is loaded and a up todate version of iscsid is running. Exiting...
Apr 24 03:34:19 mydomain named[1390]: starting BIND 9.3.6-P1-RedHat-9.3.6-25.P1.el5_11.2 -u named -t /var/named/chroot
Apr 24 03:34:19 mydomain named[1390]: adjusted limit on open files from 1024 to 1048576
Apr 24 03:34:19 mydomain named[1390]: found 8 CPUs, using 8 worker threads
Apr 24 03:34:19 mydomain named[1390]: using up to 4096 sockets
Apr 24 03:34:19 mydomain named[1390]: loading configuration from '/etc/named.conf'
Apr 24 03:34:19 mydomain named[1390]: using default UDP/IPv4 port range: [1024, 65535]
Apr 24 03:34:19 mydomain named[1390]: using default UDP/IPv6 port range: [1024, 65535]
Apr 24 03:34:19 mydomain named[1390]: listening on IPv4 interface lo, 127.0.0.1#53
Apr 24 03:34:19 mydomain named[1390]: both "recursion no;" and "allow-recursion" active
Apr 24 03:34:19 mydomain named[1390]: command channel listening on 127.0.0.1#953
Apr 24 03:34:19 mydomain named[1390]: command channel listening on ::1#953
Apr 24 03:34:19 mydomain named[1390]: zone mydomain.com/IN: loaded serial 2015042210
Apr 24 03:34:19 mydomain named[1390]: zone forum.mydomain.com/IN: loaded serial 2015042206
Apr 24 03:34:20 mydomain named[1390]: running
Apr 24 03:34:20 mydomain named[1390]: zone mydomain.com/IN: sending notifies (serial 2015042210)
Apr 24 03:34:20 mydomain named[1390]: zone forum.mydomain.com/IN: sending notifies (serial 2015042206)
Apr 24 03:34:24 mydomain xinetd[3470]: bind failed (Address already in use (errno = 98)). service = smtp
Apr 24 03:34:24 mydomain xinetd[3470]: Service smtp failed to start and is deactivated.
Apr 24 03:34:24 mydomain xinetd[3470]: xinetd Version 2.3.14 started with libwrap loadavg labeled-networking options compiled in.
Apr 24 03:34:24 mydomain xinetd[3470]: Started working: 2 available services
Apr 24 03:34:28 mydomain init: no more processes left in this runlevel

If it has been compromised, I need to backup the database at least to move it somewhere else.

Could someone help me with that? If there is some expert I would be willing to pay for the service.

Thanks
Re: OpenVZ isn't pingable after reboot [message #52945 is a reply to message #52012] Sun, 03 September 2017 02:51 Go to previous message
mangust is currently offline  mangust
Messages: 34
Registered: April 2008
Location: Spain
Member
From: *red.226.225.212.procono.es
what is:
vzctl enter ...

ip addr sh - from inside the container?

Just realized too old message

[Updated on: Sun, 03 September 2017 02:52]

Report message to a moderator

Previous Topic: Why the ploop become the default?
Next Topic: VMWare Server vs OpenVZ
Goto Forum:
  


Current Time: Tue Oct 17 04:04:23 GMT 2017