Proxmox 4.1-5/f910ef5c: server stops responding unexpectedly

[proxcraft]

Hello,

few days ago I updated my server from 3.4 version to Proxmox 4. Migration was completed without problems and server work well but after a few hours it unexpectedly stops responding and only hard reset solves the problem.

This situation repeats almost every day and I can't find solution to solve it.

Please help me.

 

[t.lamprecht]

Can you please describe your setup with more details? What storage do you use, ...

Also make loggin persistent over boots with

mkdir /var/log/journal

if you haven't already and post the log around the hang up/crash.

If you're not that familiar with systemd environment look at the journalctl manpage and/or use the following command:

journalctl b-1 > out.log # for the log from the last boot (note that there is no space between)

and post its output or the content of the created out.log file here (at best in [ code][ / code] tags).

 

[proxcraft]

out.log file is very big so I've zipped and attached the one.

 

[t.lamprecht]

what are those "no space left on device" errors

Feb 07 23:07:24 Debian-70-wheezy-64-minimal pveproxy[2396]: error writing access log
Feb 07 23:07:26 Debian-70-wheezy-64-minimal postfix/pickup[1638]: 429B2100ABA: uid=0 from=<root>
Feb 07 23:07:26 Debian-70-wheezy-64-minimal postfix/cleanup[1640]: 429B2100ABA: message-id=<20160207200726.429B2100ABA@Debian-70-wheezy-64-minimal>
Feb 07 23:07:26 Debian-70-wheezy-64-minimal postfix/cleanup[1640]: warning: 429B2100ABA: write queue file: No space left on device
Feb 07 23:07:26 Debian-70-wheezy-64-minimal postfix/pickup[1638]: warning: maildrop/60635100AEA: error writing 429B2100ABA: queue file write error
Feb 07 23:07:26 Debian-70-wheezy-64-minimal postfix/pickup[1638]: 42B2A100ABA: uid=0 from=<root>
Feb 07 23:07:26 Debian-70-wheezy-64-minimal postfix/cleanup[1640]: 42B2A100ABA: message-id=<20160207200726.42B2A100ABA@Debian-70-wheezy-64-minimal>
Feb 07 23:07:26 Debian-70-wheezy-64-minimal postfix/cleanup[1640]: warning: 42B2A100ABA: write queue file: No space left on device
Feb 07 23:07:26 Debian-70-wheezy-64-minimal postfix/pickup[1638]: warning: maildrop/4E285100909: error writing 42B2A100ABA: queue file write error
Feb 07 23:07:26 Debian-70-wheezy-64-minimal pveproxy[2396]: worker exit
Feb 07 23:07:26 Debian-70-wheezy-64-minimal pveproxy[1897]: worker 2396 finished
Feb 07 23:07:26 Debian-70-wheezy-64-minimal pveproxy[1897]: starting 2 worker(s)
Feb 07 23:07:26 Debian-70-wheezy-64-minimal pveproxy[1897]: worker 2404 started
Feb 07 23:07:26 Debian-70-wheezy-64-minimal pveproxy[1897]: worker 2405 started
Feb 07 23:07:28 Debian-70-wheezy-64-minimal pveproxy[2405]: error writing access log
Feb 07 23:07:31 Debian-70-wheezy-64-minimal pveproxy[2405]: worker exit
Feb 07 23:07:31 Debian-70-wheezy-64-minimal pveproxy[1897]: worker 2405 finished
Feb 07 23:07:31 Debian-70-wheezy-64-minimal pveproxy[1897]: starting 1 worker(s)
Feb 07 23:07:31 Debian-70-wheezy-64-minimal pveproxy[1897]: worker 2416 started
Feb 07 23:07:31 Debian-70-wheezy-64-minimal postfix/tlsmgr[2417]: error: open database /var/lib/postfix/smtpd_scache.db: No space left on device
Feb 07 23:07:31 Debian-70-wheezy-64-minimal postfix/tlsmgr[2417]: error: open database /var/lib/postfix/smtp_scache.db: No space left on device
Feb 07 23:07:31 Debian-70-wheezy-64-minimal postfix/tlsmgr[2417]: warning: btree:/var/lib/postfix/smtpd_scache is unavailable. open database /var/lib/postfix/smtpd_scache.db: No space left on device
Feb 07 23:07:31 Debian-70-wheezy-64-minimal postfix/tlsmgr[2417]: warning: btree:/var/lib/postfix/smtp_scache is unavailable. open database /var/lib/postfix/smtp_scache.db: No space left on device
Feb 07 23:07:32 Debian-70-wheezy-64-minimal pveproxy[2404]: error writing access log
Feb 07 23:07:32 Debian-70-wheezy-64-minimal postfix/smtpd[2414]: connect from unknown[195.22.126.14]
Feb 07 23:07:32 Debian-70-wheezy-64-minimal pveproxy[2404]: worker exit
Feb 07 23:07:32 Debian-70-wheezy-64-minimal pveproxy[1897]: worker 2404 finished
Feb 07 23:07:32 Debian-70-wheezy-64-minimal pveproxy[1897]: starting 1 worker(s)
Feb 07 23:07:32 Debian-70-wheezy-64-minimal pveproxy[1897]: worker 2419 started
Feb 07 23:07:32 Debian-70-wheezy-64-minimal pveproxy[2371]: error writing access log
Feb 07 23:07:32 Debian-70-wheezy-64-minimal postfix/smtpd[2414]: lost connection after AUTH from unknown[195.22.126.14]
Feb 07 23:07:32 Debian-70-wheezy-64-minimal postfix/smtpd[2414]: disconnect from unknown[195.22.126.14]

THat looks no good and more of a disk space problem then anything else.


Also I saw that you have an hetzner Server, is it a pure proxmos ISO or, proxmox on debian or some respinned ISO from hetzner? If the latter then please ask them.