similar to: /var/log/secure timestamp

Hi, I have upgraded Centos from 3.x to 4.3. The upgrade apparently didn't go too bad. I had to do the upgrade remotely, and I used as a base the post at http://www.centos.org/modules/newbb/viewtopic.php?topic_id=382 I rebooted the server, and it works. But yum does not work anymore, apparently due to some conflict between rpmlibs and selinux. This is the error that I get:

Hi, I have a problem with asterisks on Linux. Looks like it is a iptables problem. My external client (eyebeam, on a different computer) cannot register to the asterisk server, but the asterisk server itself *looks* working. If I dial one of the incoming phone numbers for the server, I can see the call arriving in Asterisk (using asterisk -r). I tried nmap on my server, and this is the result:

We have CENTOS 4.4 on DELL server. I found if I login use 'ssh" ther will have two entries on /var/log/secure. One entry use local time and another entry use "green witch time,. (I guess). It ONLY happen on ssh. Telnet, FTP and Sftp no problem. Does any one know why? Feb 28 14:01:20 ORA04 sshd[24338]: Accepted password for oracle from ::ffff:172.29.94.230 port 34470 ssh2 Feb 28

Got a strange problem here. We have OpenSSH 2.3.0p1 running on a variety of machines and on one particular Redhat 6.2 machine(all patches applied) we run into a situation where it will not allow us to start a shell when using bash or bash2. csh and others work fine. One note...if I enable PermitRootLogin, the user root IS allowed to login with bash. This is very strange. I'm guessing it

Hi all, I have a problem with the cvs head zaptel library: I cannot update my zapata.conf into asterisk when I issue the reload command from the CLI prompt; only when I stop and restart the asterisk service. The system sends the following message: Jun 20 09:49:14 WARNING[3754]: chan_zap.c:10364 setup_zap: Ignoring switchtype Jun 20 09:49:14 WARNING[3754]: chan_zap.c:10364

Hi folks, while chasing down a logging-related situation, I happened to notice that when I connect via ssh to my system it makes the following logs: Nov 15 14:15:39 saturn sshd[29868]: Accepted password for dave from ::ffff:10.0.10.14 port 2833 ssh2 Nov 15 09:15:39 saturn sshd[29867]: Accepted password for dave from ::ffff:10.0.10.14 port 2833 ssh2 Nov 15 09:15:39 saturn sshd(pam_unix)[29869]:

Hi I''ve patched net-mrtg http://www.net-snmp.org/ with http://x-ray.prokon.cz/data/snmp/ sucefully Also I''ve copied QOS.TXT to /usr/local/share/snmp/mibs when I make a normal use of snmp, with mrtg in order to monitor all traffic on eth0 and eth1, it works OK. But, how must I do in order to get monitor for a specific class ? If I make a snmpwalk (like README suggest), I get

On Mon, May 7, 2018 at 9:19 PM, Kaleb S. KEITHLEY <kkeithle at redhat.com> wrote: > > See https://review.gluster.org/19974 Many thanks Kaleb. Your patch did the trick and I did manage to compile, however I get a Segmentation fault when trying to execute gluster. I'm using the following options to configure (taken from the glusterfs 3.11.1 port in the FreeBSD port repository):

On Tue, May 8, 2018 at 11:34 AM, Roman Serbski <mefystofel at gmail.com> wrote: > # gdb gluster > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the

All of a sudden I can no longer ssh into my server running CentOS 4.5 This is what happens: [john at lt-131-jdl-f7 ~]$ ssh -Y -p 2222 192.168.0.1 john at 192.168.0.1's password: Connection to 192.168.0.1 closed by remote host. Connection to 192.168.0.1 closed. And yes, the account does exist and the password is correct! Looking at the logs, I see this: Jun 7 18:51:37 moray1

For those that might be using Cisco 7940/7960 sip phones and placing calls across an iax2 link, we think the voice quality problem has been identified and corrected. The dev cvs should be updated as of about 3:30pm CDT today (April 14). History: Calls originating from a Cisco 79x0 sip phone and sent via iax2 link to some distant * machine resulted in very poor quality audio, and in some cases,

I might be going crazy... perhaps my notes and memory has failed me but it ain't working... on host machine... ssh-keygen -t rsa ssh-keygen -t dsa scp *pub root at remote:/root on remote machine... cat /root/id_{r,d}sa.pub >> /root/.ssh/authorizedkeys_2 but it still asks for password when I try to connect as root from remote host logsAug 18 15:51:13 srv1 sshd[1630]: Accepted

Greetings. I'm running CentOS on multiple machines and a few third-party VPS's and have some odd logging issues today. It all started when tcpwrappers couldn't seem to recognize my PC's hostname as being a valid hostname for access. Fortunately I was able to get in with a direct IP. When trying to discover what's going on, I found some very odd entries in the secure

When i try to swap files between disks on my server using samba i get errors: then windows reports "The specified network name is no longer available". Sometimes the copies are fine other times files just wont copy. Hardware checks out fine. Ive even replaced the network cable between server and switch thinking that might be causing the problem. Ive included a ethereal cap of the

Hi, I'm running openldap and samba3.0.1 from my debian system, but I have used many many hours trying to get samba to validate users on the ldap... And is now turning to the last resort ... This is my configuration __________________________________________________ the important lines in smb.conf looks like this... -------------------------------------------------- [global] workgroup

> Here's the link for the maillog: > > https://paste.fedoraproject.org/paste/kbH2N9Pc~JPuCqVpE1kszQ OK. There are a couple of things: Aug 23 21:47:18 ts130 postfix/smtpd[3750]: warning: hostname localhost does not resolve to address 127.0.0.1 Aug 23 21:47:18 ts130 postfix/smtpd[3750]: connect from unknown[127.0.0.1] That needs to be fixed. What does the entry for 127.0.0.1

Hello all, I have a CentOS 4.2 server that gives me these error messages in my /var/log/secure file, I realise that these are SSH attacks, but where does the extra line "Could not get shadow information for NOUSER" come from? This doesn't make any sense. I have many servers running CentOS 4.2, but don't get this error message on any others. I hate junk in my logs. Is there

Hi! I was browsing through archives and found out that somebody else was having the same problem as I'm. http://bugzilla.mindrot.org/show_bug.cgi?id=248 from the client, when I run scp to the server, I get: scp: warning: Executing scp1 compatibility. scp: FATAL: Executing ssh1 in compatibility mode failed (Check that scp1 is in your PATH). There are more details about this problem here:

Hello, I'm using asterisk-1.0.9 and wanted to compile it with database support in voicemail (postgres). I made the following changes in the /apps/Makefile: USE_MYSQL_VM_INTERFACE=0 USE_POSTGRES_VM_INTERFACE=1 Without theese changes asterisk compiles perfectly, but after setting the postgres variable on 1 (that's what I have to do or not?), asterisk terminates with the following compile

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear dovecot developers, first: thanks for this really cool imapd, on my server it serves some hundred domains, all in all some thousand users, some having hundred thousand mails in their Maildirs (their spam boxes mostly). Since I put this installation in an FreeBSD geli encrypted disc image I had no choice but to choose an imapd with clever