Thread: system lockup
maverick 10.10, have 4 gb root partition , use 2.3 gb. attached 4 tb (2 2tb) external usb storage device test backup solution using rsync. new device generating multiple errors , errors being written syslog , dmesg logs should.
but, filled logs (df -h showed no space left on root), hence system not boot. went logs , there many syslog/dmesg ended in gz, compressed) syslog1/dmesg1.gz, syslog2/dmesg2.gz, etc. until no more space.
these logs suppose removed after reboot? script need applied clean old logs?
no, logs not removed automatically, ever, far know. typically compressed text files don't take space, , sysadmins can go thru , clean them if gets bad.
i'd have rm'ing do.
also, strikes me odd you're on 10.10. server admins run on lts releases, way have upgrade every 2 years. should @ getting off platform asap, because you're either a) in fresh install or b) lots of upgrades.
Forum The Ubuntu Forum Community Ubuntu Specialised Support Ubuntu Servers, Cloud and Juju Server Platforms [ubuntu] system lockup
Ubuntu
Comments
Post a Comment