Archive for the 'Gentoo' Category

Syslog-ng and connections exceeded error

June 2, 2007

Couple of days ago I updated my home Gentoo box and after that syslog-ng was too full of connections. As always the remedy was near.

If you have app-admin/syslog-ng-2.0.4 and get errors like

syslog-ng[8827]: Number of allowed concurrent connections exceeded; num=’10’, max=’10’

to the syslog then read this helpfull topic from Gentoo forums.

There was also note in Changelog:

2.0.4:
Mon, 14 May 2007 11:47:48 +0200

IMPORTANT NOTES:
* This version of syslog-ng fixes a bug in enforcing the max-connections() limit for various stream-like sources (unix-stream and tcp). Previously this limit was not enforced, thus production environments may use an inadequate value. Validate your max-connection() settings before upgrading and check your logs for rejected connections.

In short, just change one line in /etc/syslog-ng/syslog-ng.conf to match with:
source src { unix-stream("/dev/log" max-connections(20)); internal(); pipe("/proc/kmsg"); };

Advertisements

GWN: Do it all, minus one.

May 13, 2007

Earlier this year there was some problems updating packages and I used package.mask to get over it. There is also a better way to handle this so that the package is not updated until it’s really needed.

Gentoo Weekly Newsletter: 7 May 2007 writes about user’s problem with keeping a specific version of MythTV.

Jesse Adelman wrote into gentoo-user to ask how to be able to do an emerge -uDN world, but have portage not update one package. Jesse had a version of MythTV that had been removed from the tree that he wished to keep. However, the version in the tree was between a newer and older version, thus causing portage to want to downgrade if he simply put the newer version in package.mask.

Vikas Kumar suggested the often forgotten /etc/portage/profile/package.provided. A package placed in this file will not be updated unless another package necessarily depends on a newer version. Developer Zac Medico suggested to instead simply mask the package versions that are both higher and lower than the version Jesse wanted to keep, which is the best solution.

Using package.provided seems to be a nice solution but everything goes.