System did not come up after reboot

N

netbone

Member
Feb 5, 2009
93
0
6
System was installed and worked very well. Now I rebooted the system and Proxmox stopped working.

Any idea what happend?

PHP: 
May  5 15:25:17 ks010 kernel: ata1: SATA max UDMA/133 abar m1024@0xfe7ffc00 port 0xfe7ffd00 irq 22
May  5 15:25:17 ks010 kernel: ata2: SATA max UDMA/133 irq_stat 0x00400040, connection status changed irq 22
May  5 15:25:17 ks010 kernel: ata3: SATA max UDMA/133 abar m1024@0xfe7ffc00 port 0xfe7ffe00 irq 22
May  5 15:25:17 ks010 kernel: ata4: SATA max UDMA/133 abar m1024@0xfe7ffc00 port 0xfe7ffe80 irq 22
May  5 15:25:17 ks010 kernel: Refined TSC clocksource calibration: 2793.832 MHz.
May  5 15:25:17 ks010 kernel: Switching to clocksource tsc
May  5 15:25:17 ks010 kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
May  5 15:25:17 ks010 kernel:  alloc irq_desc for 20 on node 0
May  5 15:25:17 ks010 kernel:  alloc kstat_irqs on node 0
May  5 15:25:17 ks010 kernel: r8169 0000:03:05.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
May  5 15:25:17 ks010 kernel: r8169 0000:03:05.0: no PCI Express capability
May  5 15:25:17 ks010 kernel: eth1: RTL8169sb/8110sb at 0xffffc90012592c00, 00:e0:4c:69:12:44, XID 10000000 IRQ 20
May  5 15:25:17 ks010 kernel: pata_atiixp 0000:00:14.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16
May  5 15:25:17 ks010 kernel: pata_atiixp 0000:00:14.1: setting latency timer to 64
May  5 15:25:17 ks010 kernel: scsi4 : pata_atiixp
May  5 15:25:17 ks010 kernel: scsi5 : pata_atiixp
May  5 15:25:17 ks010 kernel: ata5: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xff00 irq 14
May  5 15:25:17 ks010 kernel: ata6: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xff08 irq 15
May  5 15:25:17 ks010 kernel: ata1: SATA link down (SStatus 0 SControl 300)
May  5 15:25:17 ks010 kernel: ata3: SATA link down (SStatus 0 SControl 300)
May  5 15:25:17 ks010 kernel: ata4: SATA link down (SStatus 0 SControl 300)
May  5 15:25:17 ks010 kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
May  5 15:25:17 ks010 kernel: ata2.00: ATA-8: Hitachi HDS721010CLA332, JP4OA39C, max UDMA/133
May  5 15:25:17 ks010 kernel: ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
May  5 15:25:17 ks010 kernel: ata2.00: configured for UDMA/133
May  5 15:25:17 ks010 kernel: scsi 1:0:0:0: Direct-Access     ATA      Hitachi HDS72101 JP4O PQ: 0 ANSI: 5
May  5 15:25:17 ks010 kernel: sd 1:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
May  5 15:25:17 ks010 kernel: sd 1:0:0:0: [sda] Write Protect is off
May  5 15:25:17 ks010 kernel: sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
May  5 15:25:17 ks010 kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May  5 15:25:17 ks010 kernel: sda: sda1 sda2 sda3
May  5 15:25:17 ks010 kernel: sd 1:0:0:0: [sda] Attached SCSI disk
May  5 15:25:17 ks010 kernel: EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts:
May  5 15:25:17 ks010 kernel: udev[374]: starting version 164
May  5 15:25:17 ks010 kernel: MCE: In-kernel MCE decoding enabled.
May  5 15:25:17 ks010 kernel: ACPI: I/O resource piix4_smbus [0xb00-0xb07] conflicts with ACPI region SOR1 [0xb00-0xb0f]
May  5 15:25:17 ks010 kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
May  5 15:25:17 ks010 kernel: EDAC MC: Ver: 2.1.0 Apr 11 2012
May  5 15:25:17 ks010 kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
May  5 15:25:17 ks010 kernel: AMD64 EDAC driver v3.4.0
May  5 15:25:17 ks010 kernel: EDAC amd64: DRAM ECC disabled.
May  5 15:25:17 ks010 kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
May  5 15:25:17 ks010 kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
May  5 15:25:17 ks010 kernel: (Note that use of the override may cause unknown side effects.)
May  5 15:25:17 ks010 kernel: [drm] Initialized drm 1.1.0 20060810
May  5 15:25:17 ks010 kernel: [drm] radeon defaulting to kernel modesetting.
May  5 15:25:17 ks010 kernel: [drm] radeon kernel modesetting enabled.
May  5 15:25:17 ks010 kernel: radeon 0000:01:05.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
May  5 15:25:17 ks010 kernel: radeon 0000:01:05.0: setting latency timer to 64
May  5 15:25:17 ks010 kernel: [drm] initializing kernel modesetting (RS880 0x1002:0x9710).
May  5 15:25:17 ks010 kernel: [drm] register mmio base: 0xFE9F0000
May  5 15:25:17 ks010 kernel: [drm] register mmio size: 65536
May  5 15:25:17 ks010 kernel: ATOM BIOS: B43106_DVI
May  5 15:25:17 ks010 kernel: radeon 0000:01:05.0: VRAM: 320M 0x00000000C0000000 - 0x00000000D3FFFFFF (320M used)
May  5 15:25:17 ks010 kernel: radeon 0000:01:05.0: GTT: 512M 0x00000000A0000000 - 0x00000000BFFFFFFF
May  5 15:25:17 ks010 kernel: [drm] Detected VRAM RAM=320M, BAR=256M
May  5 15:25:17 ks010 kernel: [drm] RAM width 32bits DDR
May  5 15:25:17 ks010 kernel: input: PC Speaker as /devices/platform/pcspkr/input/input4
May  5 15:25:17 ks010 kernel: [TTM] Zone  kernel: Available graphics memory: 8086208 kiB.
May  5 15:25:17 ks010 kernel: [TTM] Zone   dma32: Available graphics memory: 2097152 kiB.
May  5 15:25:17 ks010 kernel: [TTM] Initializing pool allocator.
May  5 15:25:17 ks010 kernel: [drm] radeon: 320M of VRAM memory ready
May  5 15:25:17 ks010 kernel: [drm] radeon: 512M of GTT memory ready.
May  5 15:25:17 ks010 kernel: [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
May  5 15:25:17 ks010 kernel: [drm] Driver supports precise vblank timestamp query.
May  5 15:25:17 ks010 kernel: [drm] radeon: irq initialized.
May  5 15:25:17 ks010 kernel: [drm] GART: num cpu pages 131072, num gpu pages 131072
May  5 15:25:17 ks010 kernel: [drm] Loading RS780 Microcode
May  5 15:25:17 ks010 kernel: platform radeon_cp.0: firmware: requesting radeon/RS780_pfp.bin
May  5 15:25:17 ks010 kernel: platform radeon_cp.0: firmware: requesting radeon/RS780_me.bin
May  5 15:25:17 ks010 kernel: platform radeon_cp.0: firmware: requesting radeon/R600_rlc.bin
May  5 15:25:17 ks010 kernel: radeon 0000:01:05.0: WB enabled
May  5 15:25:17 ks010 kernel: [drm] ring test succeeded in 1 usecs
May  5 15:25:17 ks010 kernel: [drm] radeon: ib pool ready.
May  5 15:25:17 ks010 kernel: [drm] ib test succeeded in 0 usecs
May  5 15:25:17 ks010 kernel: [drm] Radeon Display Connectors
May  5 15:25:17 ks010 kernel: [drm] Connector 0:
May  5 15:25:17 ks010 kernel: [drm]   VGA
May  5 15:25:17 ks010 kernel: [drm]   DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c
May  5 15:25:17 ks010 kernel: [drm]   Encoders:
May  5 15:25:17 ks010 kernel: [drm]     CRT1: INTERNAL_KLDSCP_DAC1
May  5 15:25:17 ks010 kernel: [drm] Connector 1:
May  5 15:25:17 ks010 kernel: [drm]   DVI-D
May  5 15:25:17 ks010 kernel: [drm]   HPD3
May  5 15:25:17 ks010 kernel: [drm]   DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c
May  5 15:25:17 ks010 kernel: [drm]   Encoders:
May  5 15:25:17 ks010 kernel: [drm]     DFP3: INTERNAL_KLDSCP_LVTMA
May  5 15:25:17 ks010 kernel: [drm] radeon: power management initialized
May  5 15:25:17 ks010 kernel: No connectors reported connected with modes
May  5 15:25:17 ks010 kernel: [drm] Cannot find any crtc or sizes - going 1024x768
May  5 15:25:17 ks010 kernel: [drm] fb mappable at 0xD0141000
May  5 15:25:17 ks010 kernel: [drm] vram apper at 0xD0000000
May  5 15:25:17 ks010 kernel: [drm] size 3145728
May  5 15:25:17 ks010 kernel: [drm] fb depth is 24
May  5 15:25:17 ks010 kernel: [drm]    pitch is 4096
May  5 15:25:17 ks010 kernel: fbcon: radeondrmfb (fb0) is primary device
May  5 15:25:17 ks010 kernel: Console: switching to colour frame buffer device 128x48
May  5 15:25:17 ks010 kernel: fb0: radeondrmfb frame buffer device
May  5 15:25:17 ks010 kernel: drm: registered panic notifier
May  5 15:25:17 ks010 kernel: Slow work thread pool: Starting up
May  5 15:25:17 ks010 kernel: Slow work thread pool: Ready
May  5 15:25:17 ks010 kernel: [drm] Initialized radeon 2.10.0 20080528 for 0000:01:05.0 on minor 0
May  5 15:25:17 ks010 kernel: Adding 4104596k swap on /dev/sda2.  Priority:-1 extents:1 across:4104596k
May  5 15:25:17 ks010 kernel: EXT3-fs: barriers disabled
May  5 15:25:17 ks010 kernel: kjournald starting.  Commit interval 5 seconds
May  5 15:25:17 ks010 kernel: EXT3-fs (sda1): using internal journal
May  5 15:25:17 ks010 kernel: EXT3-fs (sda1): mounted filesystem with ordered data mode
May  5 15:25:17 ks010 kernel: r8169 0000:02:00.0: eth0: link up
May  5 15:25:17 ks010 kernel: NET: Registered protocol family 10
May  5 15:25:17 ks010 kernel: fuse init (API version 7.13)
May  5 15:25:18 ks010 rrdcached[1447]: starting up
May  5 15:25:18 ks010 rrdcached[1447]: checking for journal files
May  5 15:25:18 ks010 rrdcached[1447]: started new journal /var/lib/rrdcached/journal//rrd.journal.1336224318.304098
May  5 15:25:18 ks010 rrdcached[1447]: journal processing complete
May  5 15:25:18 ks010 rrdcached[1447]: listening for connections
May  5 15:25:19 ks010 pmxcfs[1480]: [main] crit: Unable to get local IP address
May  5 15:25:19 ks010 postfix/master[1551]: daemon started -- version 2.7.1, configuration /etc/postfix
May  5 15:25:21 ks010 citadel: citserver: Can't bind: Address already in use
May  5 15:25:21 ks010 citadel: TCP port 0.0.0.0:25: (SMTP-MTA) FAILED.
May  5 15:25:21 ks010 citadel: Citadel had trouble on starting up. We couldn't bind all ports you configured to be provided by citadel server. This means, citadel won't be the service provider for a specific service you configured it to.#012#012If you don't want citadel to provide these services, turn them off in WebCit via Admin->System Preferences->Network.#012#012The failed ports and sockets are: TCP port 0.0.0.0;25: (SMTP-MTA) s#012#012#012If you want citadel to provide you with that functionality, check the output of "netstat -lnp" on linux Servers or "netstat -na" on *BSD and stop the programm, that binds these ports.#012 You should eventually remove  their initscripts in /etc/init.d so that you won't get this trouble once more.#012 After that goto Administration -> Shutdown Citadel to make Citadel retry to bind this port.#012#012#012To make both ways actualy take place restart the citserver with "sendcommand down"#012#012The errors returned by the system were:#012citserver: Can't bind: Address already in use; #012You can recheck the above if you follow this faq item:#012http://www.citadel.org/doku.php/faq:mastering_your_os:net#netstat
May  5 15:25:21 ks010 citadel: Startup Problems
May  5 15:25:21 ks010 citadel: 1 unique messages to be merged
May  5 15:25:21 ks010 citadel: chmod(/var/lib/citadel/data//citadel.control, 0600) returned 0
May  5 15:25:21 ks010 citadel: chown(/var/lib/citadel/data//citadel.control, CTDLUID, -1) returned 0
May  5 15:25:21 ks010 citadel: chmod(/var/lib/citadel/data//cdb.09, 0600) returned 0
May  5 15:25:21 ks010 citadel: chown(/var/lib/citadel/data//cdb.09, CTDLUID, -1) returned 0
May  5 15:25:21 ks010 citadel: chmod(/var/lib/citadel/data//cdb.00, 0600) returned 0
May  5 15:25:21 ks010 citadel: chown(/var/lib/citadel/data//cdb.00, CTDLUID, -1) returned 0
May  5 15:25:21 ks010 citadel: chmod(/var/lib/citadel/data//log.0000000001, 0600) returned 0
May  5 15:25:21 ks010 citadel: chown(/var/lib/citadel/data//log.0000000001, CTDLUID, -1) returned 0
May  5 15:25:21 ks010 citadel: chmod(/var/lib/citadel/data//cdb.08, 0600) returned 0
May  5 15:25:21 ks010 citadel: chown(/var/lib/citadel/data//cdb.08, CTDLUID, -1) returned 0
May  5 15:25:21 ks010 citadel: chmod(/var/lib/citadel/data//cdb.01, 0600) returned 0
May  5 15:25:21 ks010 citadel: chown(/var/lib/citadel/data//cdb.01, CTDLUID, -1) returned 0
May  5 15:25:21 ks010 citadel: chmod(/var/lib/citadel/data//cdb.05, 0600) returned 0
May  5 15:25:21 ks010 citadel: chown(/var/lib/citadel/data//cdb.05, CTDLUID, -1) returned 0
May  5 15:25:21 ks010 citadel: chmod(/var/lib/citadel/data//cdb.0c, 0600) returned 0
May  5 15:25:21 ks010 citadel: chown(/var/lib/citadel/data//cdb.0c, CTDLUID, -1) returned 0
May  5 15:25:21 ks010 citadel: chmod(/var/lib/citadel/data//cdb.03, 0600) returned 0
May  5 15:25:21 ks010 citadel: chown(/var/lib/citadel/data//cdb.03, CTDLUID, -1) returned 0
May  5 15:25:21 ks010 citadel: chmod(/var/lib/citadel/data//cdb.02, 0600) returned 0
May  5 15:25:21 ks010 citadel: chown(/var/lib/citadel/data//cdb.02, CTDLUID, -1) returned 0
May  5 15:25:21 ks010 citadel: chmod(/var/lib/citadel/data//cdb.0b, 0600) returned 0
May  5 15:25:21 ks010 citadel: chown(/var/lib/citadel/data//cdb.0b, CTDLUID, -1) returned 0
May  5 15:25:21 ks010 citadel: chmod(/var/lib/citadel/data//cdb.04, 0600) returned 0
May  5 15:25:21 ks010 citadel: chown(/var/lib/citadel/data//cdb.04, CTDLUID, -1) returned 0
May  5 15:25:21 ks010 citadel: chmod(/var/lib/citadel/data//citadel.config, 0600) returned 0
May  5 15:25:21 ks010 citadel: chown(/var/lib/citadel/data//citadel.config, CTDLUID, -1) returned 0
May  5 15:25:21 ks010 citadel: chmod(/var/lib/citadel/data//refcount_adjustments.dat, 0600) returned 0
May  5 15:25:21 ks010 citadel: chown(/var/lib/citadel/data//refcount_adjustments.dat, CTDLUID, -1) returned 0
May  5 15:25:21 ks010 citadel: chmod(/var/lib/citadel/data//cdb.07, 0600) returned 0
May  5 15:25:21 ks010 citadel: chown(/var/lib/citadel/data//cdb.07, CTDLUID, -1) returned 0
May  5 15:25:21 ks010 citadel: chmod(/var/lib/citadel/data//cdb.0a, 0600) returned 0
May  5 15:25:21 ks010 citadel: chown(/var/lib/citadel/data//cdb.0a, CTDLUID, -1) returned 0
May  5 15:25:21 ks010 citadel: chmod(/var/lib/citadel/data//cdb.06, 0600) returned 0
May  5 15:25:21 ks010 citadel: chown(/var/lib/citadel/data//cdb.06, CTDLUID, -1) returned 0
May  5 15:25:21 ks010 kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
May  5 15:25:21 ks010 /usr/sbin/cron[1622]: (CRON) INFO (pidfile fd = 3)
May  5 15:25:21 ks010 /usr/sbin/cron[1630]: (CRON) STARTUP (fork ok)
May  5 15:25:21 ks010 kernel: kvm: Nested Virtualization enabled
May  5 15:25:21 ks010 kernel: kvm: Nested Paging enabled
May  5 15:25:21 ks010 kernel: tun: Universal TUN/TAP device driver, 1.6
May  5 15:25:21 ks010 kernel: tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
May  5 15:25:21 ks010 /usr/sbin/cron[1630]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)
May  5 15:25:21 ks010 /usr/sbin/cron[1630]: (*system*vzdump) FSTAT FAILED (/etc/cron.d/vzdump)
May  5 15:25:21 ks010 /usr/sbin/cron[1630]: (CRON) INFO (Running @reboot jobs)
May  5 15:25:21 ks010 kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
May  5 15:25:22 ks010 kernel: RPC: Registered udp transport module.
May  5 15:25:22 ks010 kernel: RPC: Registered tcp transport module.
May  5 15:25:22 ks010 kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
May  5 15:25:22 ks010 kernel: FS-Cache: Loaded
May  5 15:25:22 ks010 kernel: FS-Cache: Netfs 'nfs' registered for caching
May  5 15:25:22 ks010 kernel: nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
May  5 15:25:25 ks010 pvedaemon[1735]: starting server
May  5 15:25:25 ks010 pvedaemon[1735]: starting 3 worker(s)
May  5 15:25:25 ks010 pvedaemon[1735]: worker 1742 started
May  5 15:25:25 ks010 pvedaemon[1735]: worker 1743 started
May  5 15:25:25 ks010 pvedaemon[1735]: worker 1744 started
May  5 15:25:26 ks010 ntpdate[904]: step time server 66.228.35.252 offset -0.012708 sec
May  5 15:25:26 ks010 kernel: eth0: no IPv6 routers present
May  5 15:25:31 ks010 kernel: venet0: no IPv6 routers present
May  5 15:25:41 ks010 ntpdate[1746]: step time server 66.228.35.252 offset -0.001268 sec
May  5 15:25:56 ks010 ntpdate[1779]: step time server 174.123.154.242 offset 0.004387 sec
May  5 15:26:16 ks010 ntpdate[1784]: step time server 66.228.35.252 offset -0.007628 sec
May  5 15:26:41 ks010 ntpdate[1797]: step time server 69.164.222.108 offset -0.003410 sec
May  5 15:27:11 ks010 ntpdate[1803]: step time server 208.87.104.40 offset -0.000976 sec
May  5 15:27:46 ks010 ntpdate[1816]: step time server 108.61.73.244 offset -0.001261 sec
May  5 15:28:26 ks010 ntpdate[1822]: step time server 108.61.73.243 offset -0.005295 sec
May  5 15:29:03 ks010 ntpd[1846]: ntpd 4.2.6p2@1.2194-o Sun Oct 17 13:35:13 UTC 2010 (1)
May  5 15:29:03 ks010 ntpd[1847]: proto: precision = 0.103 usec
May  5 15:29:03 ks010 ntpd[1847]: unable to bind to wildcard address 0.0.0.0 - another process may be running - EXITING
May  5 15:29:03 ks010 pvestatd[1872]: starting server
May  5 15:29:04 ks010 pvesh: <root@pam> starting task UPID:ks010:00000759:00005C5F:4FA52B20:startall::root@pam:
May  5 15:29:04 ks010 pvesh: writing cluster log failed: ipcc_send_rec failed: Connection refused
May  5 15:29:11 ks010 ntpdate[1841]: step time server 108.61.73.244 offset -0.002029 sec
May  5 15:29:13 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:29:13 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:29:13 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:29:13 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:29:13 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:29:14 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:29:14 ks010 task UPID:ks010:00000759:00005C5F:4FA52B20:startall::root@pam:: cluster not ready - no quorum?
May  5 15:29:14 ks010 pvesh: <root@pam> end task UPID:ks010:00000759:00005C5F:4FA52B20:startall::root@pam: cluster not ready - no quorum?
May  5 15:29:14 ks010 pvesh: writing cluster log failed: ipcc_send_rec failed: Connection refused
May  5 15:29:23 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:29:23 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:29:23 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:29:23 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:29:23 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:29:23 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:29:33 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:29:33 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:29:33 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:29:33 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:29:33 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:29:33 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:29:43 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:29:43 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:29:43 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:29:43 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:29:43 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:29:43 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:29:53 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:29:53 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:29:53 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:29:53 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:29:53 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:29:53 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:30:03 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:30:03 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:30:03 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:30:03 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:30:03 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:30:03 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:30:13 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:30:13 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:30:13 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:30:13 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:30:13 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused
May  5 15:30:13 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused

uname -a

PHP: 
Linux ks010 2.6.32-11-pve #1 SMP Wed Apr 11 07:17:05 CEST 2012 x86_64 GNU/Linux
 
May 5 15:25:19 ks010 pmxcfs[1480]: [main] crit: Unable to get local IP address
May 5 15:25:19 ks010 postfix/master[1551]: daemon started -- version 2.7.1, configuration /etc/postfix
May 5 15:25:21 ks010 citadel: citserver: Can't bind: Address already in use
May 5 15:25:21 ks010 citadel: TCP port 0.0.0.0:25: (SMTP-MTA) FAILED.
May 5 15:25:21 ks010 citadel: Citadel had trouble on starting up. We couldn't bind all ports you configured to be provided by citadel server. This means, citadel won't be the service provider for a specific service you configured it to.#012#012If you don't want citadel to provide these services, turn them off in WebCit via Admin->System Preferences->Network.#012#012The failed ports and sockets are: TCP port 0.0.0.0;25: (SMTP-MTA) s#012#012#012If you want citadel to provide you with that functionality, check the output of "netstat -lnp" on linux Servers or "netstat -na" on *BSD and stop the programm, that binds these ports.#012 You should eventually remove their initscripts in /etc/init.d so that you won't get this trouble once more.#012 After that goto Administration -> Shutdown Citadel to make Citadel retry to bind this port.#012#012#012To make both ways actualy take place restart the citserver with "sendcommand down"#012#012The errors returned by the system were:#012citserver: Can't bind: Address already in use; #012You can recheck the above if you follow this faq item:#012http://www.citadel.org/doku.php/faq:mastering_your_os:net#netstat

above is your problems. Why do you run citadel on a PVE server?

which causes this fatal error: May 5 15:29:13 ks010 pvestatd[1872]: WARNING: ipcc_send_rec failed: Connection refused​
 
I agree, but it is based on a depency in squeeze to install citadel when you install pve.

I tried again with a blank debian minimal and now it works well. Seems that maybe the os template had something special - minimal works fine.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back