Custom Query (894 matches)
Results (43 - 45 of 894)
| Ticket | Owner | Reporter | Resolution | Summary |
|---|---|---|---|---|
| #924 | desai | https://www.google.com/accounts/o8/id?id=AItOawkcSWTmDEHAW_tc0oAyhGOJhVGKEaqzSjY | worksforme | syslog to rsyslog push error |
| Description |
The following shows a run of bcfg2 on the client end. The bcfg2 config stops syslog, turns it off in chkconfig, then installs rsyslog, turns it on in chkconfig, and starts it up. This all happens, except bcfg2 never completes until I have to send a break to it when it hangs up after rsyslog starts. At the point in which I have to break it reports everything is clean. I'm not sure what is causing this, the output of a run I have to break is pasted below, it looks like bcfg2 never receives a proper complete signal from somewhere. This is a centos 5.5 kernel 2.6.18-194.8.1.el5 machine with rsyslog-3.22.1-3.el5 and bcfg2-1.0.1-1 making calls to a bcfg2-server-1.0.1-1 |
|||
| #932 | jjneely | tac_ <[email protected]…> | worksforme | centos kernel doesn't validate. rpm --validate gives no error though |
| Description |
system: centos 5 version: trunk r6046 base-packages.xml <Bundle name='base-packages'>
</Bundle> client debug: Verifying: 0:kernel-2.6.18-194.el5.x86_64
rpm -v --verify kernel-2.6.18-194.el5.x86_64 ........ /lib/modules/2.6.18-194.el5 ........ /lib/modules/2.6.18-194.el5/build ........ /lib/modules/2.6.18-194.el5/source |
|||
| #945 | desai | https://www.google.com/accounts/o8/id?id=AItOawnRppflv_a3zxygGhbfu6u4jxNS8c-fJ-E | worksforme | Reporting feature addition |
| Description |
In my environment, each SA have their own working copy of the bcfg2 repo where they make changes to and commit them after they are done. At 4pm everyday, the master bcfg2 repository (/var/lib/bcfg2) gets updated with all the changes that have been committed to the repo that day. Then from 5PM to 4AM (next day) the bcfg2 client runs on all servers and get their respective updates/config changes etc. What I would like is to get a report of exactly what is going to change on each host and/or group of hosts (based on their profile) before the changes are actually applied on each server. That way, all admins have an idea of the changes that will be happening during the night. Plus this might help us detect a unintentional catastrophic change before it is actually applied to the servers. Thanks, much. -pedro |
|||
