That was probably my fault-- Thunderbird doesn't seem to recognize the correct recipient (when clicking "reply") so I had to "reply to all" instead so you received one message directly from me and another from me via this list.
If the DH deamon does eventually die, hopefully the log will indicate the issue. I know there was discussion about the daemon dying recently but I believed that had something to do with my broken gateway device for the sync server (you have sync disabled). Phil On Thu, 26 Jun 2008, James Carman wrote: > Oops, I didn't realize that this list actually sends the emails with > the reply-to address as the sender and not the list. > > > ---------- Forwarded message ---------- > From: James Carman <[EMAIL PROTECTED]> > Date: Thu, Jun 26, 2008 at 10:27 AM > Subject: Re: [Denyhosts-user] Denyhosts daemon dying on startup... > To: Phil Schwartz <[EMAIL PROTECTED]> > > > The --debug flag doesn't appear to work for my restart (or merely > start for that matter). However, using the command line that it spits > out in /var/log/denyhosts, I tried starting the daemon manually using > that command and I get: > > 2008-06-26 10:22:57,948 - denyhosts : INFO DenyHosts launched > with the following args: > 2008-06-26 10:22:57,948 - denyhosts : INFO > /usr/bin/denyhosts.py --daemon --config=/etc/denyhosts.conf --debug > 2008-06-26 10:22:57,949 - prefs : INFO DenyHosts > configuration settings: > 2008-06-26 10:22:57,949 - prefs : INFO ADMIN_EMAIL: > [EMAIL PROTECTED] > 2008-06-26 10:22:57,949 - prefs : INFO AGE_RESET_INVALID: > [864000] > 2008-06-26 10:22:57,950 - prefs : INFO > AGE_RESET_RESTRICTED: [2160000] > 2008-06-26 10:22:57,950 - prefs : INFO AGE_RESET_ROOT: [2160000] > 2008-06-26 10:22:57,950 - prefs : INFO AGE_RESET_VALID: [432000] > 2008-06-26 10:22:57,950 - prefs : INFO > ALLOWED_HOSTS_HOSTNAME_LOOKUP: [YES] > 2008-06-26 10:22:57,951 - prefs : INFO BLOCK_SERVICE: [sshd] > 2008-06-26 10:22:57,951 - prefs : INFO DAEMON_LOG: > [/var/log/denyhosts] > 2008-06-26 10:22:57,951 - prefs : INFO > DAEMON_LOG_MESSAGE_FORMAT: [%(asctime)s - %(name)-12s: %(levelname)- > 8s %(message)s] > 2008-06-26 10:22:57,951 - prefs : INFO > DAEMON_LOG_TIME_FORMAT: [None] > 2008-06-26 10:22:57,952 - prefs : INFO DAEMON_PURGE: [3600] > 2008-06-26 10:22:57,952 - prefs : INFO DAEMON_SLEEP: [30] > 2008-06-26 10:22:57,952 - prefs : INFO DENY_THRESHOLD_INVALID: > [5] > 2008-06-26 10:22:57,952 - prefs : INFO > DENY_THRESHOLD_RESTRICTED: [1] > 2008-06-26 10:22:57,953 - prefs : INFO DENY_THRESHOLD_ROOT: [1] > 2008-06-26 10:22:57,953 - prefs : INFO DENY_THRESHOLD_VALID: [10] > 2008-06-26 10:22:57,953 - prefs : INFO FAILED_ENTRY_REGEX: [None] > 2008-06-26 10:22:57,953 - prefs : INFO FAILED_ENTRY_REGEX2: > [None] > 2008-06-26 10:22:57,954 - prefs : INFO FAILED_ENTRY_REGEX3: > [None] > 2008-06-26 10:22:57,954 - prefs : INFO FAILED_ENTRY_REGEX4: > [None] > 2008-06-26 10:22:57,954 - prefs : INFO FAILED_ENTRY_REGEX5: > [None] > 2008-06-26 10:22:57,954 - prefs : INFO FAILED_ENTRY_REGEX6: > [None] > 2008-06-26 10:22:57,955 - prefs : INFO FAILED_ENTRY_REGEX7: > [None] > 2008-06-26 10:22:57,955 - prefs : INFO HOSTNAME_LOOKUP: [YES] > 2008-06-26 10:22:57,955 - prefs : INFO HOSTS_DENY: > [/etc/hosts.deny] > 2008-06-26 10:22:57,955 - prefs : INFO LOCK_FILE: > [/var/lock/subsys/denyhosts] > 2008-06-26 10:22:57,955 - prefs : INFO PLUGIN_DENY: [None] > 2008-06-26 10:22:57,956 - prefs : INFO PLUGIN_PURGE: [None] > 2008-06-26 10:22:57,956 - prefs : INFO PURGE_DENY: [2419200] > 2008-06-26 10:22:57,956 - prefs : INFO PURGE_THRESHOLD: [0] > 2008-06-26 10:22:57,957 - prefs : INFO RESET_ON_SUCCESS: [no] > 2008-06-26 10:22:57,957 - prefs : INFO SECURE_LOG: > [/var/log/secure] > 2008-06-26 10:22:57,957 - prefs : INFO SMTP_DATE_FORMAT: > [%a, %d %b %Y %H:%M:%S %z] > 2008-06-26 10:22:57,957 - prefs : INFO SMTP_FROM: > [DenyHosts <[EMAIL PROTECTED]>] > 2008-06-26 10:22:57,958 - prefs : INFO SMTP_HOST: [localhost] > 2008-06-26 10:22:57,958 - prefs : INFO SMTP_PASSWORD: [None] > 2008-06-26 10:22:57,958 - prefs : INFO SMTP_PORT: [25] > 2008-06-26 10:22:57,958 - prefs : INFO SMTP_SUBJECT: > [DenyHosts Report from terminator] > 2008-06-26 10:22:57,959 - prefs : INFO SMTP_USERNAME: [None] > 2008-06-26 10:22:57,959 - prefs : INFO SSHD_FORMAT_REGEX: [None] > 2008-06-26 10:22:57,959 - prefs : INFO > SUCCESSFUL_ENTRY_REGEX: [None] > 2008-06-26 10:22:57,959 - prefs : INFO > SUSPICIOUS_LOGIN_REPORT_ALLOWED_HOSTS: [YES] > 2008-06-26 10:22:57,960 - prefs : INFO SYNC_DOWNLOAD: [yes] > 2008-06-26 10:22:57,960 - prefs : INFO > SYNC_DOWNLOAD_RESILIENCY: [18000] > 2008-06-26 10:22:57,960 - prefs : INFO SYNC_DOWNLOAD_THRESHOLD: > [3] > 2008-06-26 10:22:57,960 - prefs : INFO SYNC_INTERVAL: [3600] > 2008-06-26 10:22:57,961 - prefs : INFO SYNC_SERVER: [None] > 2008-06-26 10:22:57,961 - prefs : INFO SYNC_UPLOAD: [yes] > 2008-06-26 10:22:57,961 - prefs : INFO SYSLOG_REPORT: [no] > 2008-06-26 10:22:57,961 - prefs : INFO WORK_DIR: > [/var/lib/denyhosts] > 2008-06-26 10:22:57,976 - denyhosts : INFO restricted: set([]) > 2008-06-26 10:22:57,977 - filetracker : DEBUG __get_current_offset(): > 2008-06-26 10:22:57,977 - filetracker : DEBUG first_line: Jun 22 > 06:08:42 terminator sshd[16336]: refused connect > from ::ffff:59.151.26.115 (::ffff:59.151.26.115) > 2008-06-26 10:22:57,977 - filetracker : DEBUG offset: 231509 > 2008-06-26 10:22:57,978 - AllowedHosts: DEBUG initializing AllowedHosts > 2008-06-26 10:22:57,978 - AllowedHosts: DEBUG line: 127.0.0.1 - > regex match? True > 2008-06-26 10:22:57,979 - AllowedHosts: DEBUG allowed_hosts: > ['localhost.localdomain', '127.0.0.1'] > 2008-06-26 10:22:57,979 - AllowedHosts: DEBUG done initializing > AllowedHosts > 2008-06-26 10:22:57,980 - filetracker : DEBUG __get_last_offset(): > 2008-06-26 10:22:57,980 - filetracker : DEBUG first_line: Jun 22 > 06:08:42 terminator sshd[16336]: refused connect > from ::ffff:59.151.26.115 (::ffff:59.151.26.115) > 2008-06-26 10:22:57,980 - filetracker : DEBUG offset: 231509 > 2008-06-26 10:22:57,980 - filetracker : DEBUG get_offset(): > 2008-06-26 10:22:57,981 - filetracker : DEBUG offset: None > 2008-06-26 10:22:57,981 - denyhosts : INFO launching DenyHosts > daemon (version 2.6)... > 2008-06-26 10:22:57,985 - denyhosts : INFO DenyHosts daemon is > now running, pid: 7709 > 2008-06-26 10:22:57,986 - denyhosts : INFO send daemon process a > TERM signal to terminate cleanly > 2008-06-26 10:22:57,986 - denyhosts : INFO eg. kill -TERM 7709 > 2008-06-26 10:22:57,993 - denyhosts : INFO monitoring log: > /var/log/secure > 2008-06-26 10:22:57,994 - denyhosts : INFO sync_time: 3600 > 2008-06-26 10:22:57,994 - denyhosts : INFO daemon_purge: 3600 > 2008-06-26 10:22:57,994 - denyhosts : INFO daemon_sleep: 30 > 2008-06-26 10:22:57,995 - denyhosts : INFO purge_sleep_ratio: 120 > 2008-06-26 10:22:57,995 - denyhosts : INFO denyhosts > synchronization disabled > > > Now, when I do "service denyhosts status" I get: > > denyhosts.py (pid 7709) is running... > > So, I know it can run successfully using the same command line (I just > added --debug to the end of it), so I'm really puzzled as to why it's > not working correctly when running it with my init.d script (I > installed this using yum and I haven't monkeyed with anything in the > init.d script). > > On Thu, Jun 26, 2008 at 10:15 AM, Phil Schwartz > <[EMAIL PROTECTED]> wrote: >> >> Try restarting it in debug mode: >> >> service denyhosts restart --debug >> >> should do the trick. Perhaps the denyhosts.log will indicate some >> weirdness. >> >> Regards, >> >> Phil >> >> >> >> James Carman wrote: >>> >>> I have started seeing login attempts in my LogWatch emails. I thought >>> Denyhosts was supposed to take care of that, so I logged in and >>> checked to see if it was running by doing "service denyhosts status" >>> and it says that it is stopped. So, I start it up using "service >>> denyhosts start" and everything looks good in /var/log/denyhosts: >>> >>> 2008-06-26 07:22:48,463 - denyhosts : INFO launching DenyHosts >>> daemon (version 2.6)... >>> 2008-06-26 07:22:48,468 - denyhosts : INFO DenyHosts daemon is >>> now running, pid: 6895 >>> 2008-06-26 07:22:48,470 - denyhosts : INFO send daemon process a >>> TERM signal to terminate cleanly >>> 2008-06-26 07:22:48,470 - denyhosts : INFO eg. kill -TERM 6895 >>> >>> Then, I do "service denyhosts status" and I get: >>> >>> denyhosts.py is stopped >>> >>> It seems to be dying for some reason. Has anyone else seen this? I >>> am running version "denyhosts-2.6-7.fc8". >>> >>> One thing that I did do today was to enable NTP sync on my server, but >>> these issues were happening before that. >>> >>> ------------------------------------------------------------------------- >>> Check out the new SourceForge.net Marketplace. >>> It's the best place to buy or sell services for >>> just about anything Open Source. >>> http://sourceforge.net/services/buy/index.php >>> _______________________________________________ >>> Denyhosts-user mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/denyhosts-user >>> >>> >> > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Denyhosts-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/denyhosts-user > -- Regards, Phil Schwartz - http://www.phil-schwartz.com Open Source Projects: - DenyHosts: http://www.denyhosts.net - Kodos: http://kodos.sourceforge.net - ReleaseForge: http://releaseforge.sourceforge.net - Scratchy: http://scratchy.sourceforge.net - FAQtor: http://faqtor.sourceforge.net ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Denyhosts-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/denyhosts-user
