Custom Query (894 matches)
Results (121 - 123 of 894)
| Ticket | Owner | Reporter | Resolution | Summary |
|---|---|---|---|---|
| #280 | desai | naapuri | fixed | bcfg2 incorrectly reports "All entries correct." |
| Description |
Suppose that a config file belonging to a .deb package is changed, eg. /etc/screenrc. Running bcfg2 without -q notices this change and re-installs the 'screen' package. However, config files are not overwritten when re-installing packages (and they shouldn't be). So bcfg2 ends up re-installing 'screen' every time it is run, and still claiming "All entries correct." even though they are not. The best fix I can think of for this problem (and other similar problems - I think these exist!) would be to re-run bcfg2 with -n whenever bcfg2 made choices and thought that everything was fixed. This should be done internally in bcfg2, and by default. This will slow down the bcfg2 client, but only when there is something to fix. |
|||
| #281 | desai | naapuri | fixed | bcfg2-server silently allows multiple instances |
| Description |
bcfg2-server seems to allow multiple instances to be listening on the same port. (I didn't know this was even possible!) This might cause confusion. How to reproduce (at least on my debian etch with svn build 2531):
# netstat -plunt Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 x.x.x.x:6789 0.0.0.0:* LISTEN 3909/python tcp 0 0 x.x.x.x:6789 0.0.0.0:* LISTEN 3906/python (...) How to fix: bcfg2-server should detect the situation where someone is already listening on the port and refuse to start. |
|||
| #282 | desai | naapuri | fixed | bcfg2-server starts serving before it is ready |
| Description |
When testing bcfg2, I occasionally get errors such as Incomplete information for entry ConfigFile:/etc/motd; cannot install and on respectively on the server: Failed to bind entry: ConfigFile /etc/motd It took me a while to realize that this occurs when I've just restarted the bcfg2-server and then run the client too quickly. How to reproduce:
A correct run: # bcfg2-server /etc/bcfg2.pem Bound to port 6789 Processed 23 gamin events in 6.161 seconds. 0 collapsed Processed 3 gamin events in 0.100 seconds. 0 collapsed Processed 3 gamin events in 0.100 seconds. 0 collapsed Generated config for etchbase in 0.0238389968872 seconds Client etchbase reported state clean An incorrect run: # bcfg2-server /etc/bcfg2.pem Bound to port 6789 Processed 23 gamin events in 6.081 seconds. 0 collapsed Processed 3 gamin events in 0.101 seconds. 0 collapsed Failed to bind entry: ConfigFile /etc/motd Generated config for etchbase in 0.024423122406 seconds Processed 3 gamin events in 0.101 seconds. 0 collapsed Client etchbase reported state dirty How to fix: the server should first read the config and only then start listening on the port. |
|||
