Why can't I re-install rsyslog?

SamTzu

Renowned Member
Have you noticed this..?

root@serverX:~# apt-get remove rsyslog

Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
gdisk hdparm ipset libicu48 libipset2 libmime-base32-perl libmnl0 libnetfilter-log1 liboath0 libuuid-perl novnc-pve oathtool powermgmt-base python-suds spiceterm
Use 'apt-get autoremove' to remove them.

The following extra packages will be installed:
pve-kernel-2.6.32-33-pve

The following packages will be REMOVED:
clvm fence-agents-pve libpve-access-control libpve-storage-perl librados2-perl proxmox-ve-2.6.32 pve-cluster pve-firewall pve-manager qemu-server redhat-cluster-pve resource-agents-pve rsyslog vzctl
The following NEW packages will be installed:
pve-kernel-2.6.32-33-pve
0 upgraded, 1 newly installed, 14 to remove and 4 not upgraded.
Need to get 34.5 MB of archives.
 
Hi,
but this is normal, because pve-cluster depends on rsyslog:
Code:
dpkg -I /var/cache/apt/archives/pve-cluster_3.0-15_amd64.deb 
 new debian package, version 2.0.
 size 146570 bytes: control archive=2022 bytes.
      72 bytes,     3 lines      conffiles            
     724 bytes,    12 lines      control              
    1015 bytes,    15 lines      md5sums              
    1350 bytes,    56 lines   *  postinst             #!/bin/sh
    1074 bytes,    44 lines   *  postrm               #!/bin/sh
     198 bytes,     7 lines   *  prerm                #!/bin/sh
 Package: pve-cluster
 Version: 3.0-15
 Architecture: amd64
 Maintainer: Proxmox Support Team <support@proxmox.com>
 Installed-Size: 444
 Depends: libc6 (>= 2.2.5), libcorosync4-pve, libfuse2 (>= 2.9.2-4), libglib2.0-0 (>= 2.31.8), libqb0, librrd4 (>= 1.4~rc2), libsqlite3-0 (>= 3.6.0), perl (>= 5.14.2-21+deb7u1), perlapi-5.14.2, rsync, sqlite3, fuse, libpve-common-perl, [B]rsyslog[/B], openssl, librrds-perl, rrdcached, libdigest-hmac-perl, libxml-parser-perl, insserv
 Section: admin
 Priority: optional
 Description: Cluster Infrastructure for Proxmox Virtual Environment
  This package contains the Cluster Infrastructure for the Proxmox
  Virtual Environment, namely a distributed filesystem to store
  configuration data on all nodes.
And re-install isn't "apt-get remove"!!

The better approach was
Code:
apt-get --reinstall install rsyslog
Udo
 
This is the result...

2526.366203581:7f1ca6c01700: rsyslogd 5.8.11 startup, compatibility mode 5, module path '', cwd:/media/local4/private2526.366437827:7f1ca6c01700: caller requested object 'net', not found (iRet -3003)
2526.366461503:7f1ca6c01700: Requested to load module 'lmnet'
2526.366472049:7f1ca6c01700: loading module '/usr/lib/rsyslog/lmnet.so'
2526.374590895:7f1ca6c01700: module of type 2 being loaded.
2526.374601860:7f1ca6c01700: entry point 'isCompatibleWithFeature' not present in module
2526.374610311:7f1ca6c01700: source file conf.c requested reference for module 'lmnet', reference count now 1
2526.374635104:7f1ca6c01700: rsyslog runtime initialized, version 5.8.11, current users 1
2526.374692443:7f1ca6c01700: source file syslogd.c requested reference for module 'lmnet', reference count now 2
2526.375061692:7f1ca6c01700: GenerateLocalHostName uses 'hp1'
2526.375084949:7f1ca6c01700: omfile: using transactional output interface.
2526.375135932:7f1ca6c01700: module of type 1 being loaded.
2526.375148783:7f1ca6c01700: module of type 1 being loaded.
2526.375157793:7f1ca6c01700: entry point 'beginTransaction' not present in module
2526.375164427:7f1ca6c01700: entry point 'endTransaction' not present in module
2526.375173646:7f1ca6c01700: source file omfwd.c requested reference for module 'lmnet', reference count now 3
2526.375196554:7f1ca6c01700: module of type 1 being loaded.
2526.375205075:7f1ca6c01700: entry point 'doHUP' not present in module
2526.375211360:7f1ca6c01700: entry point 'beginTransaction' not present in module
2526.375218344:7f1ca6c01700: entry point 'endTransaction' not present in module
2526.375228262:7f1ca6c01700: module of type 1 being loaded.
2526.375236643:7f1ca6c01700: entry point 'doHUP' not present in module
2526.375243068:7f1ca6c01700: entry point 'beginTransaction' not present in module
2526.375249424:7f1ca6c01700: entry point 'endTransaction' not present in module
2526.375258224:7f1ca6c01700: module of type 1 being loaded.
2526.375266604:7f1ca6c01700: entry point 'doHUP' not present in module
2526.375272820:7f1ca6c01700: entry point 'beginTransaction' not present in module
2526.375279315:7f1ca6c01700: entry point 'endTransaction' not present in module
2526.375287417:7f1ca6c01700: module of type 1 being loaded.
2526.375295798:7f1ca6c01700: entry point 'doHUP' not present in module
2526.375302083:7f1ca6c01700: entry point 'beginTransaction' not present in module
2526.375308858:7f1ca6c01700: entry point 'endTransaction' not present in module
2526.375321150:7f1ca6c01700: rfc5424 parser init called
2526.375327994:7f1ca6c01700: GetParserName addr 0x414120
2526.375334490:7f1ca6c01700: module of type 3 being loaded.
2526.375344197:7f1ca6c01700: Parser 'rsyslog.rfc5424' added to list of available parsers.
2526.375353207:7f1ca6c01700: rfc3164 parser init called
2526.375360191:7f1ca6c01700: module of type 3 being loaded.
2526.375368223:7f1ca6c01700: Parser 'rsyslog.rfc3164' added to list of available parsers.
2526.375375416:7f1ca6c01700: Parser 'rsyslog.rfc5424' added to default parser set.
2526.375381772:7f1ca6c01700: Parser 'rsyslog.rfc3164' added to default parser set.
2526.375389245:7f1ca6c01700: rsyslog standard file format strgen init called, compiled with version 5.8.11
2526.375396368:7f1ca6c01700: module of type 4 being loaded.
2526.375403073:7f1ca6c01700: entry point 'isCompatibleWithFeature' not present in module
2526.375412362:7f1ca6c01700: Strgen 'RSYSLOG_FileFormat' added to list of available strgens.
2526.375419416:7f1ca6c01700: traditional file format strgen init called, compiled with version 5.8.11
2526.375426330:7f1ca6c01700: module of type 4 being loaded.
2526.375432895:7f1ca6c01700: entry point 'isCompatibleWithFeature' not present in module
2526.375440298:7f1ca6c01700: Strgen 'RSYSLOG_TraditionalFileFormat' added to list of available strgens.
2526.375447492:7f1ca6c01700: rsyslog standard (network) forward format strgen init called, compiled with version 5.8.11
2526.375454406:7f1ca6c01700: module of type 4 being loaded.
2526.375460901:7f1ca6c01700: entry point 'isCompatibleWithFeature' not present in module
2526.375468304:7f1ca6c01700: Strgen 'RSYSLOG_ForwardFormat' added to list of available strgens.
2526.375475288:7f1ca6c01700: rsyslog traditional (network) forward format strgen init called, compiled with version 5.8.11
2526.375482482:7f1ca6c01700: module of type 4 being loaded.
2526.375488907:7f1ca6c01700: entry point 'isCompatibleWithFeature' not present in module
2526.375496101:7f1ca6c01700: Strgen 'RSYSLOG_TraditionalForwardFormat' added to list of available strgens.
2526.375615179:7f1ca6c01700: Checking pidfile.
Already running. If you want to run multiple instances, you need to specify different pid files (use -i option)
 
This is the result...
Code:
Already running. If you want to run multiple instances, you need to specify different pid files (use -i option)
Hi,
this shows that your rsyslogd is running - where is the problem?

See
Code:
ps aux | grep rsyslog

To run rsyslogd in foreground makes only sense if no other rsyslogd run.

Udo
 
Problem is the syslog is empty. The rsyslog.conf file is identical with other cluster members and those work fine.

we just recently discovered a rsyslog problem on some wheezy hosts, probably induced by some updates in the past - symptoms could be similar to yours: logfiles seem to remain empty, but in fact, the damon just logs into the last *rotated* one (means, e.g. "messages" remains empty, but "messages.1" is filled).

We fixed that this way:
service rsyslog stop
rm /var/run/rsyslogd.pid
service rsyslog start
 

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!

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!