Bug#735186: Problem with diff report
Hello, You can close this bug. It has been solved after changing the CVS configuration. Best regard. -- Vincent LOUPIEN - Direction des Systemes d'Information Batiment Ampere D - Bureau 035 101 rue de la Physique F-38400 SAINT MARTIN D HERES Tel : (+33).04.57.42.13.39 - Fax : (+33).04.57.42.13.62
Bug#735186: Problem with diff report
Hi Roland, No changes have been made ??to the configuration of Rancid during the migration phase from Squeeze to Wheezy. That's what I thought, but what changes does rancid report? Does it report everything changed (maybe because the line ends differ) or does it report only changes in some comments (for example the time stamp of the configuration or something like this)? Does rancid report the changes on every run? If so, how do the changes vary from report to report? If not, you may have a problem with CVS/SVN, where the data is stored? All devices configurations changes are reported. For cons, I just noticed that the version numbers are not changed and I soupsonne more and more the version control system CVS to be responsible for this incident. I will study and test in this sense. Best regard, -- Bug cvswebBEGIN:VCARD VERSION:3.0 FN:Vincent LOUPIEN N:LOUPIEN;Vincent;;; ADR;TYPE=work,postal,parcel:;;Direction des Systemes d'Information,Universite Pierre Mendes-France,Batiment Langues\, Nouvelles Technologies - Bureau 23,Domaine Universitaire,1300\, rue des Résidences - BP 47 Cedex 9;Grenoble;;F-38040; TEL;TYPE=work,fax:(+33).4.76.82.83.13 TEL;TYPE=work,voice:(+33).4.76.82.57.58 EMAIL;TYPE=internet:vincent.loup...@upmf-grenoble.fr URL;TYPE=work:http://webdsi.upmf-grenoble.fr/connecteur_php_5.1/BiperV4/infosplus_carte.php?personne=1218 REV:2013-03-22T14:01:40Z UID:c675c308-6f59-46f5-9589-14e7e4524794:2249 END:VCARD
Bug#735186: Problem with diff report
Hello Roland! - Mail original - Hi Vincent! On Mon, 13 Jan 2014, Vincent LOUPIEN wrote: Since the migration of Debian 6 Squeeze in Debian 7.2 Wheezy , there is a problem with the generation of the daily report of differences . In this report indicated all configurations of all networks equipements that have experienced a change in theirs configurations. Can you give more concrete information what changed? Is it every single line of every config or is it only some special part of the config? No changes have been made to the configuration of Rancid during the migration phase from Squeeze to Wheezy. What type of devices (vendor) do you collect data from? Only devices from Cisco Catalyst and HP Procurve series. We manage 3 sites that are running more than 150 facilities , each of our sites have its own Rancid (with an identical configuration) and the 3 Rancid have exactly the same bad behavior and generate daily messages more and longer ... and finaly unworkable. I have to admit, that we still run squeeze on our production rancid systems, but with a (recompiled) wheezy rancid version. We didn't notice any problems with this setup on our devices. I did not dare get into a test from sources Rancid, I focus on using Debian package. I think this problem comes from running the new version of Debian or a side effect of migration (libraries, dependences, etc ...). Machines from which run my Rancid also host other services such as MRTG, Nagios, Syslog-ng, Apache2 ... and everything works wonders. So you should give me more input what exactly goes wrong. No problem: tell me what data do you need to advance your investigation: conf, log, others information ... ? Thank you for your quick reply :-) -- BEGIN:VCARD VERSION:3.0 FN:Vincent LOUPIEN N:LOUPIEN;Vincent;;; ADR;TYPE=work,postal,parcel:;;Direction des Systemes d'Information,Universite Pierre Mendes-France,Batiment Langues\, Nouvelles Technologies - Bureau 23,Domaine Universitaire,1300\, rue des Résidences - BP 47 Cedex 9;Grenoble;;F-38040; TEL;TYPE=work,fax:(+33).4.76.82.83.13 TEL;TYPE=work,voice:(+33).4.76.82.57.58 EMAIL;TYPE=internet:vincent.loup...@upmf-grenoble.fr URL;TYPE=work:http://webdsi.upmf-grenoble.fr/connecteur_php_5.1/BiperV4/infosplus_carte.php?personne=1218 REV:2013-03-22T14:01:40Z UID:c675c308-6f59-46f5-9589-14e7e4524794:2249 END:VCARD
Bug#735186: Problem with diff report
Package: rancid Version: 2.3.8-3 Our company uses Rancid (from Debian package) for many years with satisfaction. Since the migration of Debian 6 Squeeze in Debian 7.2 Wheezy , there is a problem with the generation of the daily report of differences . In this report indicated all configurations of all networks equipements that have experienced a change in theirs configurations. We manage 3 sites that are running more than 150 facilities , each of our sites have its own Rancid (with an identical configuration) and the 3 Rancid have exactly the same bad behavior and generate daily messages more and longer ... and finaly unworkable. During migration , I have taken into account the differences in configuration between the old version 2.3.3-2 and new 2.3.8-3 but it does not seem to come from there. I looked on the side of official support (forum , internet search ... ) Rancid without success. Do you have an idea or can come this problem ? or tracks lesquelle to advance my research ? Thank you in advance for your help. I am using Debian GNU/Linux 7.2, kernel 3.2.0-4-686-pae and libc6:i386 2.13-38 . -- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#560192: The Netdisco changelog doesnt exist in package
Packages: netdisco-common and netdisco-frontend Version: 1.0-1 Same problem from the new stable release. The home page of Netdisco provides the user a link to the details of the version and the link / netdisco / doc / changelog.txt points to a nonexistent file. I suggested to correct this bugs in future stable version of this package. I am using Debian GNU/Linux 6.0.4, kernel 2.6.32-5-686 and libc6 2.11.3-2. -- Vincent LOUPIEN - Direction des Systemes d'Information Batiment Langues, Nouvelles Technologies - Bureau 37 Universite Pierre Mendes France (Grenoble 2) 79, rue des Universites - BP 47 - F-38040 Grenoble Cedex 9 Tel : (+33).04.76.82.57.58 - Fax : (+33).04.76.82.83.13 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#560192: The Netdisco changelog doesnt exist in package
Package: netdisco-common Version: 0.95-3 On the home page of the interface (web) of netdisco, in the New in 0.95 box, the link to the changelog of version (/ netdisco / doc / ChangeLog.txt) does not provide in the package netdisco-common, or in the dependent packages to. I suggested to add in future versions of this package. I am using Debian GNU/Linux 5.0r3, kernel 2.6.26-19lenny2 and libc6 2.7-18. -- Vincent LOUPIEN - Direction des Systemes d'Information Batiment Langues, Nouvelles Technologies - Bureau 303 Universite Pierre Mendes France - Domaine Universitaire 79, rue des Universites - BP 47 - F-38040 Grenoble Cedex 9 Tel : (+33).04.76.82.57.58 - Fax : (+33).04.76.82.83.13 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#550076: Fwd: Cause of error in syslog-ng.conf not comprehensible
Package: syslog-ng
Version: 2.0.9-4.1
Since i upgraded my syslog-ng service version 2.0.0-1etch1 to 2.0.9-4.1
(Lenny), my log refer to each reload of the service, error messages under the
form syslog-ng[]: Internal error, duplicate configuration elements refer to
the same persistent config; name='affile_dd_writers(/var/log/hosts/$HOST.log)'.
I can not find the source of the error in my conf, especially since I have not
changed anything in it. Conf tests with syslog-ng-sv do not return any
error and i searched in the doc of Syslog-NG (balabit.com), with google and
various other forums. This same behavior occurs on each of my servers (x3)
using syslog-ng.
Do you have an idea or it may come ? your help will be very useful.
I follow to you the conf syslog-ng (syslog-ng.conf) one of my servers.
I am using Debian GNU/Linux 5.0, kernel 2.6.26-2-686 and libc6 2.7-18.
--
Vincent LOUPIEN - Direction des Systemes d'Information
Batiment Langues, Nouvelles Technologies - Bureau 303
Universite Pierre Mendes France - Domaine Universitaire
79, rue des Universites - BP 47 - F-38040 Grenoble Cedex 9
Tel : (+33).04.76.82.57.58 - Fax : (+33).04.76.82.83.13
#
# Configuration file for syslog-ng under Debian
#
# attempts at reproducing default syslog behavior
# the standard syslog levels are (in descending order of priority):
# emerg alert crit err warning notice info debug
# the aliases error, panic, and warn are deprecated
# the none priority found in the original syslogd configuration is
# only used in internal messages created by syslogd
##
# options
options {
# disable the chained hostname format in logs
# (default is enabled)
chain_hostnames(0);
# the time to wait before a died connection is re-established
# (default is 60)
time_reopen(10);
# the time to wait before an idle destination file is closed
# (default is 60)
time_reap(360);
# the number of lines buffered before written to file
# you might want to increase this if your disk isn't catching with
# all the log messages you get or if you want less disk activity
# (say on a laptop)
# (default is 0)
#sync(0);
# the number of lines fitting in the output queue
log_fifo_size(2048);
# enable or disable directory creation for destination files
create_dirs(yes);
# default owner, group, and permissions for log files
# (defaults are 0, 0, 0600)
#owner(root);
group(adm);
perm(0640);
# default owner, group, and permissions for created directories
# (defaults are 0, 0, 0700)
#dir_owner(root);
#dir_group(root);
dir_perm(0755);
# enable or disable DNS usage
# syslog-ng blocks on DNS queries, so enabling DNS may lead to
# a Denial of Service attack
# (default is yes)
#use_dns(no);
use_dns(yes);
# maximum length of message in bytes
# this is only limited by the program listening on the /dev/log Unix
# socket, glibc can handle arbitrary length log messages, but -- for
# example -- syslogd accepts only 1024 bytes
# (default is 2048)
#log_msg_size(2048);
#Disable statistic log messages.
stats_freq(0);
# Some program send log messages through a private implementation.
# and sometimes that implementation is bad. If this happen syslog-ng
# may recognise the program name as hostname. Whit this option
# we tell the syslog-ng that if a hostname match this regexp than that
# is not a real hostname.
#bad_hostname(^gconfd$);
};
##
# sources
# vl : message syslog (udp/514) de toutes les interfaces ip(0.0.0.0)
source s_syslog {
udp(ip(0.0.0.0) port(514));
};
# all known message sources
source s_all {
# message generated by Syslog-NG
internal();
# standard Linux log source (this is the default place for the syslog()
# function to send logs to)
unix-stream(/dev/log);
# messages from the kernel
file(/proc/kmsg log_prefix(kernel: ));
# use the above line if you want to receive remote UDP logging messages
# (this is equivalent to the -r syslogd flag)
#udp();
};
##
# destinations
# vl
destination d_lugia {
file(/var/log/hosts/$HOST.log owner(root) group(adm) perm(0640));
};
destination d_lugiam {
file(/var/log/hosts/$HOST.log owner(root) group(adm) perm(0640));
};
destination d_c1130-lm-1 {
file(/var/log/hosts/$HOST.log owner(root) group(adm) perm(0640));
};
destination d_c1130-lm-2 {
file(/var/log/hosts/$HOST.log owner(root) group(adm) perm(0640));
};
destination d_c1130-lm-3 {
file(/var/log/hosts/$HOST.log owner(root) group(adm) perm(0640
Bug#428424: syslog-ng : numerous facilities are ignored after upgrade to Etch
Package: syslog-ng Version: 2.0.0-1 After an normal upgrade Sarge (stable) to Etch (Stable), all log (local and remote) recevied via syslog services goes into /var/log/syslog as a result and not to her log file destination. The same conf was running fine in the previous version in Sarge. I've verify this conf, restarted several of the daemons since and syslog-ng ignores some of my facilities that i set. I've seen no error in the log about the restart of syslog-ng : Jun 11 17:44:13 samahe syslog-ng[5429]: SIGTERM received, terminating; Jun 11 17:44:13 samahe syslog-ng[5429]: syslog-ng shutting down; version='2.0.0' Jun 11 17:44:13 samahe syslog-ng[17491]: syslog-ng starting up; version='2.0.0' Linux samahe 2.6.18-4-686 #1 SMP Wed May 9 23:03:12 UTC 2007 i686 GNU/Linux Libc6 Version: 2.3.6.ds1-13 Thanks in advance for your help. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#350693: ntop command script need more improvements
Package: ntop Version: 2:3.0-5 When i invoke the ntop command script to restart it with crond (/etc/init.d/ntop restart), I have got some errors in it's execution, like : Stopping network top daemon: /etc/init.d/ntop: line 31: start-stop-daemon: command not found Ntop not stopped. Need to kill manually. Starting network top daemon: /etc/init.d/ntop: line 19: start-stop-daemon: command not found When i invoke it from command line or with the webmin module crond, the same command works fine ! After a little research, it seems to miss the $PATH in this script with the minimals bin directories, like : PATH=/sbin:/bin:/usr/sbin:/usr/bin Thanks and best regards for all jobs ... -- Vincent LOUPIEN - Centre de Ressources Informatiques Batiment Langues, Nouvelles Technologies - Bureau 303 Universite Pierre Mendes France - Domaine Universitaire 79, rue des Universites - BP 47 - F-38040 Grenoble Cedex 9 Tel : (+33).04.76.82.57.58 - Fax : (+33).04.76.82.83.13 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
