On Mon, 18 Jun 2012 12:34:49 +0200 "Alberto Fuentes
alberto.fuen...@qindel.com" suggested this:
>If you dont have any raid and it changed names for you too maybe is
>not just my raid case :S
I don't have any raid aL.
My external hard drive mounts with UUID and also says that /media/usb0
is mou
On 06/18/2012 11:57 AM, Charlie wrote:
[...]
does it shift between remounts or does it shift names live?
It used to shift live.
[...]
Maybe with raid the problem is different?
Well, its a hardware raid and its presented to the system as a single
disk. I have to pass a few parameters to
On Mon, 18 Jun 2012 08:44:42 +0200 "Alberto Fuentes
alberto.fuen...@qindel.com" suggested this:
>On 06/16/2012 02:31 PM, Charlie wrote:
>> It changes the device from /dev/sdb1 to /dev/sdd1 and back again.
>>
>> I am now mounting it as /dev/sdb1. That's what it has always been,
>> and then it sta
On 06/16/2012 02:31 PM, Charlie wrote:
It changes the device from /dev/sdb1 to /dev/sdd1 and back again.
I am now mounting it as /dev/sdb1. That's what it has always been, and
then it started to drop out while I was looking through the files and
wouldn't mount and came up as /dev/sdd1 etc..
It
Good time of the day, Charlie.
You worte:
> It changes the device from /dev/sdb1 to /dev/sdd1 and back again.
Oh, I got it now - You did not mention that.
> I am now mounting it as /dev/sdb1. That's what it has always been, and
> then it started to drop out while I was looking through the file
On Sun, 17 Jun 2012 08:43:49 +1000, Charlie wrote:
> On Sat, 16 Jun 2012 17:13:26 + (UTC) "Camaleón noela...@gmail.com"
> suggested this:
>>Being USB volumes in external enclosures it can be that they were badly
>>umounted and thus the message. I would run "fsck" over the umounted
>>volumes
On Sun, 17 Jun 2012 10:45:26 +0100 "keith km3...@gmail.com" suggested
this:
>On Sat, 2012-06-16 at 22:31 +1000, Charlie wrote:
>
>> It changes the device from /dev/sdb1 to /dev/sdd1 and back again.
>>
>> I am now mounting it as /dev/sdb1. That's what it has always been,
>> and then it started t
On Sat, 2012-06-16 at 22:31 +1000, Charlie wrote:
> It changes the device from /dev/sdb1 to /dev/sdd1 and back again.
>
> I am now mounting it as /dev/sdb1. That's what it has always been, and
> then it started to drop out while I was looking through the files and
> wouldn't mount and came up as
On Sat, 16 Jun 2012 17:13:26 + (UTC) "Camaleón noela...@gmail.com"
suggested this:
>On Sat, 16 Jun 2012 08:14:03 +1000, Charlie wrote:
>
>> This happens with both powered and powered only through a USB
>> connection, external hard drives. Both with ext3 file systems:
>>
>> Message from sysl
On Sat, 16 Jun 2012 08:14:03 +1000, Charlie wrote:
> This happens with both powered and powered only through a USB
> connection, external hard drives. Both with ext3 file systems:
>
> Message from syslogd@nomad at Jun 16 08:04:30 ... kernel:[ 3187.986721]
> journal commit I/O error
Being USB vol
On Sat, 16 Jun 2012 11:30:34 +0700 "Sthu Deus sthu.d...@gmail.com"
suggested this:
>> mount /mnt/lpics
>> mount: special device /dev/sdd1 does not exist
>
>Why don't You mount /dev/sdb1 but /dev/sdd1 ?
>
>Also, You can mount by UUID.
>
>What I would do in Your situation is:
>
>. connect HDD d
Good time of the day, Charlie.
You worte:
> Tried different cabling:
>
> blkid says,
>
> /dev/sdb1: UUID="4bb48afe-02d7-487f-a51f-ff378edbc98d" TYPE="ext3"
>
> Then in a terminal:
>
> mount /mnt/lpics
> mount: special device /dev/sdd1 does not exist
Why don't You mount /dev/sdb1 but /dev/s
On Fri, 15 Jun 2012 23:48:12 +0700 "Sthu Deus sthu.d...@gmail.com"
suggested this:
>Good time of the day, Charlie.
>
>
>You worte:
>
>> This happens with both powered and powered only through a
>> USB connection, external hard drives. Both with ext3 file systems:
>>
>> Message from syslogd@noma
Good time of the day, Charlie.
You worte:
> This happens with both powered and powered only through a
> USB connection, external hard drives. Both with ext3 file systems:
>
> Message from syslogd@nomad at Jun 16 08:04:30 ...
> kernel:[ 3187.986721] journal commit I/O error
>
> Seems to be more
On Fri, 15 Jun 2012 14:21:00 +0200 "Alberto Fuentes
alberto.fuen...@qindel.com" suggested this:
>On 06/16/2012 12:14 AM, Charlie wrote:
>>
>> This happens with both powered and powered only through a
>> USB connection, external hard drives. Both with ext3 file systems:
>>
>> Message from syslogd
On 06/16/2012 12:14 AM, Charlie wrote:
This happens with both powered and powered only through a
USB connection, external hard drives. Both with ext3 file systems:
Message from syslogd@nomad at Jun 16 08:04:30 ... kernel:[ 3187.986721]
journal commit I/O error
This seems regular error in disk
On Sat, Nov 12, 2005 at 12:34:28PM +0100, Roy wrote:
> In /var/log/messages the following lines are apprearing:
Good... they're supposed to be. Means your machine is alive and syslog is
running.
> What is the correct command to use in debian?
Why stop them?
--
Marc Wilson | I must follo
On 12:34 Sat 12 Nov , Roy wrote:
> In /var/log/messages the following lines are apprearing:
>
> Date Time machine name -- MARK --
> Date Time machine name -- MARK --
> Date Time machine name -- MARK --
>
> I'm using the following command, below to get rid of them, but i'm getting an
>
On Thu, Dec 02, 2004 at 05:54:19PM -0800, jack kinnon wrote:
> I'm still stuck with this problem.
>
> syslogd : cannot create /dev/log : address family not supported by protocol
>
> The whole system is working only in basic command-line mode. Someone
> suggested downloading the 'Debian Installe
> HI,
>
> I'm still stuck with this problem.
>
> syslogd : cannot create /dev/log : address family not supported by
> protocol
I didn't notice that you have asked before, so I don't know what has already
been suggested... but if the _address family_ is unsupported, then you
should compile your
I found the problem!
- Original Message -
From:
dizma
To: [EMAIL PROTECTED]
Sent: Tuesday, September 24, 2002 4:44
PM
Subject: syslogd $ logrotate
Hi there,
I'm running Woody
My syslog daemon doesn't log any thing after
logrotate was run?
NN
Raffaele Sandrini, 2001-Nov-09 19:13 +0100:
> Hi all,
>
> what do i have to enter to the sylog.conf to split all the iptables messages
> done by the LOG (-j LOG) target into another file than messages?
>
> cheers,
> Raffaele
> --
syslog doesn't allow this functionality. You need to replace it
On Fri, Jul 06, 2001 at 04:38:10PM -0500, Leonard Leblanc wrote:
> Hello,
>
> I am currently running Kernel 2.2.19pre17. I recently recompiled it to
> support Generic SCSI devices (this is the only thing that I added). I then
> restarted and from some reason (which I don't even have the slight
On Sun, Jan 21, 2001 at 02:18:38AM -0500, Arcady Genkin wrote:
> Hmm. And from where did you think I pulled out that one? :^)
>
> ,[ syslog.conf(5) ]
> |The facility is one of the following keywords: auth, auth
> |priv, cron, daemon, kern, lpr, mail, mark, news, security
>
Arcady Genkin wrote:
> mike polniak <[EMAIL PROTECTED]> writes:
>
> > > As I wrote in my previous message, ever since I added "cron.!info;" to
> > > the line that pipes to /dev/xconsole, I am not seeing the exim cron
> > > notifications any more.
> >
> > Did you mean : cron.!=info; ?
> >
mike polniak <[EMAIL PROTECTED]> writes:
> > As I wrote in my previous message, ever since I added "cron.!info;" to
> > the line that pipes to /dev/xconsole, I am not seeing the exim cron
> > notifications any more.
>
> Did you mean : cron.!=info; ?
>^^
Thank yo
>
> As I wrote in my previous message, ever since I added "cron.!info;" to
> the line that pipes to /dev/xconsole, I am not seeing the exim cron
> notifications any more.
Did you mean : cron.!=info; ?
^^
--
~~~
"Noah L. Meyerhans" <[EMAIL PROTECTED]> writes:
> There's no such syslog facility "cron". Cron logs to the 'daemon'
> facility. The only way to tweak what cron messages you see is to adjust
> what daemon priorities get logged. Read the syslog and syslog.conf man
> pages.
Hmm. And from where d
On Sat, Jan 20, 2001 at 06:36:44PM -0500, Arcady Genkin wrote:
> "Noah L. Meyerhans" <[EMAIL PROTECTED]> writes:
>
> > Well, if you look at the line that's logged, you'll see that it's not
> > coming from Exim at all, but from cron. So changing the way syslog
> > handles the mail facility won't h
"Noah L. Meyerhans" <[EMAIL PROTECTED]> writes:
> Well, if you look at the line that's logged, you'll see that it's not
> coming from Exim at all, but from cron. So changing the way syslog
> handles the mail facility won't help.
Yes, that's why I tried adding "cron.!*" to the rule. But it see
mike polniak <[EMAIL PROTECTED]> writes:
> > How would I get rid of the message about exim cron job being printed
> > at /dev/xconsole? This job runs every 20 minutes and I would like not
> > to see reports of it unless there was an error.
> >
> Edit /etc/cron.d/exim file.
This would let
Arcady Genkin wrote:
> How would I get rid of the message about exim cron job being printed
> at /dev/xconsole? This job runs every 20 minutes and I would like not
> to see reports of it unless there was an error.
>
> , [ /dev/xconsole ]
> | Jan 20 14:38:01 tea /USR/SBIN/CRON[5850]: (mail) C
Well, if you look at the line that's logged, you'll see that it's not
coming from Exim at all, but from cron. So changing the way syslog
handles the mail facility won't help. Also, exim is configured by
default (on debian) to handle its own logging and not go through syslog.
The cron logs come f
server. I will have to look into that more..
Thanks
-Original Message-
From: kmself@ix.netcom.com [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 19, 2000 12:49 PM
To: debian-user@lists.debian.org
Subject: Re: Syslogd
On Thu, Oct 19, 2000 at 11:36:52AM -0700, Jay Kelly ([EMAIL
Jay Kelly <[EMAIL PROTECTED]> writes:
> When I bootup my system hangs on "Starting System Log Daemon
> Systlogd" how can I troubleshot this to see whats happening? Thanks
Try to boot in single user mode, then the sysklogd won't start
automatically. To boot in a different runlevel, just append th
On Thu, Oct 19, 2000 at 11:36:52AM -0700, Jay Kelly ([EMAIL PROTECTED]) wrote:
> Hello All,
> When I bootup my system hangs on
> "Starting System Log Daemon Systlogd" how can I troubleshot this to see
> whats happening?
Boot single user and attempt to start the daemon in debug mode from the
comman
cool, thanks!
On Wed, 2 Aug 2000, Bill Goudie wrote:
bgoudi >On Tue, Aug 01, 2000 at 11:19:49PM -0700, [EMAIL PROTECTED] wrote:
bgoudi >> i just got a cisco675 for my dsl today and noticed it supports
syslog, i
bgoudi >> want to get it to send log entries to one of my boxes, is there
anything
b
On Tue, Aug 01, 2000 at 11:19:49PM -0700, [EMAIL PROTECTED] wrote:
> i just got a cisco675 for my dsl today and noticed it supports syslog, i
> want to get it to send log entries to one of my boxes, is there anything
> special i have to do to syslogd to allow this? i didnt see anything
The default
On Tue, Sep 07, 1999 at 12:21:21AM +0200, Pere Camps wrote:
> Hi!
>
> How can I make syslogd mail somebody an incident (aka log) when it
> happens?
There isn't support for email in syslogd, though the remote logging
feature (line with @hostname as the action in syslog.conf) may be close
eno
Horacio, near the tail end of the linux kernel README file, Linus
suggests what to do in case of a crash. (Wow... This is actually my first
crash-incident involving the kernel! I have seen X die once before, and I
had to login remotely and reboot in order to get the thing back... but this
is the fi
On Wed, 12 Nov 1997, E.L. Meijer (Eric) wrote:
> I think I found what caused it: I recently purged inn from the system.
> In the /etc/syslog.conf file there were lines about files that weren't
> there anymore:
>
> # Logging for INN news system
> #
> news.crit /var/log/news/n
>
> Hi,
>
> Since I changed some packages and removed some others syslogd is
> constantly running on a rex/bit-of-bo system. It appends messages to
> /var/log/messages like
>
> Nov 12 11:12:05 pebbles syslogd: select: Bad file number
> Nov 12 11:12:36 pebbles last message repeated 204124 times
Make sure all of the files in syslogd.conf exist.
Bruce
--
Bruce Perens K6BP [EMAIL PROTECTED] 510-215-3502
Finger [EMAIL PROTECTED] for PGP public key.
PGP fingerprint = 88 6A 15 D0 65 D4 A3 A6 1F 89 6A 76 95 24 87 B3
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "uns
On 15:25:22 Hamish Moffatt wrote:
>>On Sat, Apr 05, 1997 at 11:04:39AM -0700, Rick Macdonald wrote:
>> Speaking of syslogd, when I boot the machine it hangs for 5 ro 10 seconds
>> when syslogd starts. It didn't used to.
>> I'm running from unstable. Anybody know what it's doing?
>
>Does this here
Elie Rosenblum writes:
> On Sat, 5 Apr 1997, Ken Gaugler wrote:
> > According to the manpages,
> >
> >-n Avoid auto-backgrounding. This is needed especially
> > if the syslogd is started and controlled by
> > init(8).
> > My system, originally a 1.1
Moin Ken!
> > Ken Gaugler writes:
> >
> > > > > For some reason syslogd refuses to start in the /etc/init.d/sysklogd
> > > > > file. The docs say to use a -n command line argument if starting
> > > > > syslogd from the inits, but at bootup I see the message
> > > > > "-n unknown option" and it s
On Sat, Apr 05, 1997 at 11:04:39AM -0700, Rick Macdonald wrote:
> Speaking of syslogd, when I boot the machine it hangs for 5 ro 10 seconds
> when syslogd starts. It didn't used to.
> I'm running from unstable. Anybody know what it's doing?
Does this here too ... Keeps the machine at high CPU load
On Sat, 5 Apr 1997, Ken Gaugler wrote:
> According to the manpages,
>
>-n Avoid auto-backgrounding. This is needed especially
> if the syslogd is started and controlled by
> init(8).
> My system, originally a 1.1 system, has syslog starting from the
Martin Schulze wrote:
>
> Ken Gaugler writes:
>
> > > > For some reason syslogd refuses to start in the /etc/init.d/sysklogd
> > > > file. The docs say to use a -n command line argument if starting
> > > > syslogd from the inits, but at bootup I see the message
> > > > "-n unknown option" and it
Ken Gaugler writes:
> > > For some reason syslogd refuses to start in the /etc/init.d/sysklogd
> > > file. The docs say to use a -n command line argument if starting
> > > syslogd from the inits, but at bootup I see the message
> > > "-n unknown option" and it still doesn't start.
> >
> > becaus
On Apr 5, Rick Macdonald wrote
> On Sat, 5 Apr 1997, Rick Macdonald wrote:
>
> > Here's mine. I didn't change mine either!
> >
> >
> > case "$1" in
> > start)
> > echo -n "Starting system log daemon: syslogd"
> > start-stop-daemon --start --quiet --exec /sbin/syslogd -- $SYSLOGD
>
> S
[EMAIL PROTECTED] wrote:
>
> >
> > For some reason syslogd refuses to start in the /etc/init.d/sysklogd
> > file. The docs say to use a -n command line argument if starting
> > syslogd from the inits, but at bootup I see the message
> > "-n unknown option" and it still doesn't start.
>
> because
On Sat, 5 Apr 1997, Rick Macdonald wrote:
> Here's mine. I didn't change mine either!
>
>
> case "$1" in
> start)
> echo -n "Starting system log daemon: syslogd"
> start-stop-daemon --start --quiet --exec /sbin/syslogd -- $SYSLOGD
Speaking of syslogd, when I boot the machine it hangs
On Sat, 5 Apr 1997, Ken Gaugler wrote:
> For some reason syslogd refuses to start in the /etc/init.d/sysklogd
> file. The docs say to use a -n command line argument if starting
> syslogd from the inits, but at bootup I see the message
> "-n unknown option" and it still doesn't start.
> Here are
John Timmers:
> I've just installed bash_2.0-2 and sysklogd_1.3-14 among other things
> (but these are relevant to the question) and generally the bootup
> sequence hangs for 10 seconds, just after syslogd is started, and just
> before klogd starts. There are no error messages in any of the logs,
Thank you all that answered my questions about syslog repeated
messages.
It really was the "news" lines in syslog.conf. Just commenting them
worked out the problem.
Thank you again, and happy new year for all!
Fernando
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
> On the following problem, I just found out that this is a syslogd
> internal message. It comes after syslogd restarts. It's like this:
>
> - Dec 22 06:49:31 blackbird syslogd 1.3-0#11: restart.
> - Dec 22 06:49:31 blackbird syslogd: select: Bad file number
> - Dec 22 06:50:02 blackbird last mess
In your email to me, F. Fernandez, you wrote:
>
> Hi!
>
> On the following problem, I just found out that this is a syslogd
> internal message. It comes after syslogd restarts. It's like this:
>
> - Dec 22 06:49:31 blackbird syslogd 1.3-0#11: restart.
> - Dec 22 06:49:31 blackbird syslogd: selec
I was having the same problem. What you need to do is a 'uname -a' from
that get your hostname and make sure there is an entry in the /etc/hosts
file for both that hostname and the hostname.domainname, if you are using
dynamic ip w/ ppp just set your hostname to 127.0.0.1.
-Michael
On Thu, 3 Oc
>
> Some versions of sysklogd die at bootup when your net is not running
> (as in under ppp). Adding entries in /etc/hosts may solve your
> problem. See a recent thread in the comp.os.linux groups...
Thanks, that did it!
For the record, here's the solution to this problem:
Ed Merrifield ([EM
Joey Hess <[EMAIL PROTECTED]> writes:
>
> I'm having a problem with the sysklogd package. Sometimes when I boot up,
> it says it's starting syslogd, waits there for about a minute (much longer
> than usual), and then continues on to start klogd. It looks like syslogd
> isn't really starting when
On Tue, 6 Aug 1996, Dermot Bradley wrote:
> On Sat, 3 Aug 1996, llucius wrote:
>
> > Make sure you have a domainname set or apply patch found in bug #3526.
>
> Hmm #3526 isn't on the UK bugs site.
>
I might have gotten the # wrong, but the latest sysklogd (1.3-10) has the
patch applied. (It's
On Sat, 3 Aug 1996, llucius wrote:
> Make sure you have a domainname set or apply patch found in bug #3526.
Hmm #3526 isn't on the UK bugs site.
Dermot
--
Dermot BradleyEmail: [EMAIL PROTECTED]
Communications Director Tel: 01232 560552
Gene
On Sat, 3 Aug 1996, Dermot Bradley wrote:
> I'm running Debian 1.1 on a machine here and as of a few days ago syslogd
> has stopped working. If I run the daemon manually it runs for about 30
> seconds and then stops. I've tried removing the sysklogd package (using
> the --force option) and re-i
On Sat, 3 Aug 1996, Dermot Bradley wrote:
> I'm running Debian 1.1 on a machine here and as of a few days ago syslogd
> has stopped working. If I run the daemon manually it runs for about 30
> seconds and then stops. I've tried removing the sysklogd package (using
> the --force option) and re-i
65 matches
Mail list logo
