Le 12-06-2023, à 21:25:40 +0200, Michel Verdier a écrit :
On 2023-06-11, steve wrote:
After a few days with this configuration, same errors are still present.
I guess I'll have either to reinstall or go the postfix way.
Just to be sure before you reinstall can you provide
exim -bP | grep sy
On 2023-06-11, steve wrote:
>>> After a few days with this configuration, same errors are still present.
>>>
>>> I guess I'll have either to reinstall or go the postfix way.
>>
>>Just to be sure before you reinstall can you provide
>>exim -bP | grep syslog
>
> syslog_duplication
Docs indicate it
Hi Michel,
Le 10-06-2023, à 11:19:25 +0200, Michel Verdier a écrit :
On 2023-06-10, steve wrote:
Hi Michel and al,
After a few days with this configuration, same errors are still present.
I guess I'll have either to reinstall or go the postfix way.
Just to be sure before you reinstall can
On 2023-06-10, steve wrote:
> Hi Michel and al,
>
> After a few days with this configuration, same errors are still present.
>
> I guess I'll have either to reinstall or go the postfix way.
Just to be sure before you reinstall can you provide
exim -bP | grep syslog
Hi Michel and al,
After a few days with this configuration, same errors are still present.
I guess I'll have either to reinstall or go the postfix way.
Have a nice day,
steve
Le 05-06-2023, à 10:50:00 +0200, Michel Verdier a écrit :
Le 5 juin 2023 Steve a écrit :
if one succeed without me
Le 05-06-2023, à 10:50:00 +0200, Michel Verdier a écrit :
Le 5 juin 2023 Steve a écrit :
if one succeed without message and with code 0, add in
/etc/logrotate.d/exim4-base and /etc/logrotate.d/exim4-paniclog
postrotate
systemctl exim4-base
endscript
if you add reload but still get
Le 5 juin 2023 Steve a écrit :
>>if one succeed without message and with code 0, add in
>>/etc/logrotate.d/exim4-base and /etc/logrotate.d/exim4-paniclog
>>
>>postrotate
>>systemctl exim4-base
>>endscript
>>
>>if you add reload but still get the error try restart, I don't know if
>>th
Le 05-06-2023, à 10:21:52 +0200, Michel Verdier a écrit :
Le 5 juin 2023 Steve a écrit :
Merci pour ton aide Michel.
De rien :) Let's continue in english for the list
Sure.
log_file_path = /var/log/exim4/%slog
log_selector = +smtp_protocol_error +smtp_syntax_error
+tls_certificate_verif
Le 5 juin 2023 Steve a écrit :
> Merci pour ton aide Michel.
De rien :) Let's continue in english for the list
> log_file_path = /var/log/exim4/%slog
> log_selector = +smtp_protocol_error +smtp_syntax_error
> +tls_certificate_verified +tls_peerdn
exim writes directly to the logfiles. If you ge
Le 05-06-2023, à 09:09:05 +0200, Michel Verdier a écrit :
Le 5 juin 2023 Steve a écrit :
Yes, nothing is done after rotation. But I don't remember the default
exim logging mechanism. Can you provide
grep -r log_file_path /etc/exim*
This gives nothing.
Then can you provide
exim -bP
(snip i
Le 5 juin 2023 Steve a écrit :
>>Yes, nothing is done after rotation. But I don't remember the default
>>exim logging mechanism. Can you provide
>>
>>grep -r log_file_path /etc/exim*
>
> This gives nothing.
Then can you provide
exim -bP
(snip ip adresses if you want)
Le 04-06-2023, à 19:11:57 +0200, Michel Verdier a écrit :
Le 4 juin 2023 Steve a écrit :
Does this help?
Yes, nothing is done after rotation. But I don't remember the default
exim logging mechanism. Can you provide
grep -r log_file_path /etc/exim*
This gives nothing.
Le 4 juin 2023 Steve a écrit :
> Does this help?
Yes, nothing is done after rotation. But I don't remember the default
exim logging mechanism. Can you provide
grep -r log_file_path /etc/exim*
Le 04-06-2023, à 14:30:08 +0200, Michel Verdier a écrit :
Le 4 juin 2023 Steve a écrit :
2023-06-04T06:30:54.117016+02:00 box exim[24894]: 2023-06-04 06:30:54
1q5fOD-0006TT-2C failed to write to main log: length=91 result=-1 errno=9 (Bad
file descriptor)
2023-06-04T06:30:54.150516+02:00 box
Le 4 juin 2023 Steve a écrit :
> 2023-06-04T06:30:54.117016+02:00 box exim[24894]: 2023-06-04 06:30:54
> 1q5fOD-0006TT-2C failed to write to main log: length=91 result=-1 errno=9
> (Bad file descriptor)
> 2023-06-04T06:30:54.150516+02:00 box exim[24894]: write failed on panic log:
Hi,
Running Debian bookworm fully updated.
Since a couple of weeks, i see strange lines in the logs:
2023-06-04T06:30:54.117016+02:00 box exim[24894]: 2023-06-04 06:30:54
1q5fOD-0006TT-2C failed to write to main log: length=91 result=-1 errno=9 (Bad
file descriptor)
2023-06-04T06:30
nks, it fixes the problem indeed.
>
> I am quite disappointed by deja-dup front-end as Nicolas George points
> out and I will recommend to not use it. I will directly use duplicity
> instead in the future.
I would like to moderate the interpretation of my statement. I said that
"bad
Hi.
On Sat, 8 Jul 2017 20:42:00 +0200
Pétùr wrote:
> Le 08/07/2017 à 18:34, Reco a écrit :
> >> Any idea?
> >>
> >> $ duplicity restore --gio --time=2017-07-06T08:14:08Z --force
> >> file:///home/pierre/data/backup_pierre / --verbosity=9
> >> --gpg-options=--no-use-agent --archive-dir=/h
Le 08/07/2017 à 18:37, Nicolas George a écrit :
> Le decadi 20 messidor, an CCXXV, Nicolas George a écrit :
>> This specific error message is always the sign of a severe bug in the
>> program.
> Hum, I had not imagined the wrong file descriptor was requested on
> purpose. The severe bug was not in
Le 08/07/2017 à 18:34, Reco a écrit :
>> Any idea?
>>
>> $ duplicity restore --gio --time=2017-07-06T08:14:08Z --force
>> file:///home/pierre/data/backup_pierre / --verbosity=9
>> --gpg-options=--no-use-agent --archive-dir=/home/pierre/.cache/deja-dup
>> --tempdir=/tmp --log-fd=22
> Sure. Don't ask
Le decadi 20 messidor, an CCXXV, Nicolas George a écrit :
> This specific error message is always the sign of a severe bug in the
> program.
Hum, I had not imagined the wrong file descriptor was requested on
purpose. The severe bug was not in the program but in the caller.
Regards,
--
Nicolas
Le decadi 20 messidor, an CCXXV, Pétùr a écrit :
> "OSError: [Errno 9] Bad file descriptor"
This specific error message is always the sign of a severe bug in the
program. One that leaves 0 confidence in said program.
If it comes from you backup program, it is entirely possible your
Hi.
On Sat, 8 Jul 2017 18:28:49 +0200
Pétùr wrote:
> Any idea?
>
> $ duplicity restore --gio --time=2017-07-06T08:14:08Z --force
> file:///home/pierre/data/backup_pierre / --verbosity=9
> --gpg-options=--no-use-agent --archive-dir=/home/pierre/.cache/deja-dup
> --tempdir=/tmp --log-fd
e a backup made with deja-dup. The recovery
gets stuck quickly.
I tried to pass the duplicity command manually and here is the error :
"OSError: [Errno 9] Bad file descriptor"
It happens no matter which backup I choose to restore.
I am running Debian unstable.
Any idea?
$ duplicity
atar wrote:
> I have in my machine a directory that has the value of '000' as its
> permissions and even when I switch to the root account (using the
> 'su' command), I'm not able to 'chown' it nor to 'chmod' it nor to
> delete it. so my question is simply how can I deal with such a
> directory or
On Sun, 22 Dec 2013 17:17:59 +0200
atar wrote:
> Hi there!!
>
> I have in my machine a directory that has the value of '000' as its
> permissions and even when I switch to the root account (using the
> 'su' command), I'm not able to 'chown' it nor to 'chmod' it nor to
> delete it. so my questio
Hi there!!
I have in my machine a directory that has the value of '000' as its permissions
and even when I switch to the root account (using the 'su' command), I'm not
able to 'chown' it nor to 'chmod' it nor to delete it. so my question is
simply how can I deal with such a directory or file?
atar wrote:
> I have in my machine a directory that has the value of '000' as its
> permissions and even when I switch to the root account (using the
> 'su' command), I'm not able to 'chown' it nor to 'chmod' it nor to
> delete it. so my question is simply how can I deal with such a
> directory or
atar writes:
> Hi there!!
>
> I have in my machine a directory that has the value of '000' as its
> permissions and even when I switch to the root account (using the 'su'
> command), I'm not able to 'chown' it nor to 'chmod' it nor to delete
> it. so my question is simply how can I deal with su
Hi there!!
I have in my machine a directory that has the value of '000' as its
permissions and even when I switch to the root account (using the 'su'
command), I'm not able to 'chown' it nor to 'chmod' it nor to delete it.
so my question is simply how can I deal with such a directory or fi
Dennis Wicks wrote the following on 05/01/2012 06:20 PM:
Greetings;
I have a file that looks like the following in an ls list;
-? ? ? ? ? ? Inbox.msf
I can't do anything with it. Can't mv, rm, cp, or anything
else I have thought of to get rid of it or write over it.
Any ideas how I ca
Jochen Spieker wrote:
Dan B.:
No. Losing the display order setting is probably the _worst-case_
scenario
The OP showed us an obvious case of file system corruption. He is lucky
if he only lost this index file and no other files. He is *very* lucky
if an fsck can repair the damage and nothing
On Thu, 03 May 2012 13:35:51 -0400, Dan wrote in message
<4fa2c1f7.9020...@kempt.net>:
> Arnt Karlsen wrote:
> > On Wed, 02 May 2012 15:39:05 -0400, Dan wrote in message
> > ...
> >>> ..if Inbox.msf is your email,...
> >> That looks like a Mozilla SeaMonkey or Thunderbird mail _index_
> >> file.
Dan B.:
>
> No. Losing the display order setting is probably the _worst-case_
> scenario
The OP showed us an obvious case of file system corruption. He is lucky
if he only lost this index file and no other files. He is *very* lucky
if an fsck can repair the damage and nothing else is corrupted.
Arnt Karlsen wrote:
On Wed, 02 May 2012 15:39:05 -0400, Dan wrote in message
...
..if Inbox.msf is your email,...
That looks like a Mozilla SeaMonkey or Thunderbird mail _index_ file.
If it is, it can be deleted and SeaMonkey/Thunderbird will re-create
it (from the corresponding mail data file
On Tue, May 01, 2012 at 06:20:11PM -0500, Dennis Wicks wrote:
> Greetings;
>
> I have a file that looks like the following in an ls list;
>
> -? ? ?? ?? Inbox.msf
>
> I can't do anything with it. Can't mv, rm, cp, or anything else I
> have thought of to ge
On Wed, 02 May 2012 15:39:05 -0400, Dan wrote in message
<4fa18d59.9010...@kempt.net>:
> Arnt Karlsen wrote:
> > On Wed, 2 May 2012 07:04:55 +0200, Jochen wrote in message
> > <20120502050455.ga25...@well-adjusted.de>:
> >
> >> Dennis Wicks:
> >>> Greetings;
> >>>
> >>> I have a file that looks
On Wed, May 2, 2012 at 12:04 AM, Jochen Spieker wrote:
> Dennis Wicks:
>> Greetings;
>>
>> I have a file that looks like the following in an ls list;
>>
>> -? ? ? ? ? ? Inbox.msf
>>
>> I can't do anything with it. Can't mv, rm, cp, or anything else I
>> have t
Arnt Karlsen wrote:
On Wed, 2 May 2012 07:04:55 +0200, Jochen wrote in message
<20120502050455.ga25...@well-adjusted.de>:
Dennis Wicks:
Greetings;
I have a file that looks like the following in an ls list;
-? ? ?? ?? Inbox.msf
I can't do anything wit
nd the file's inode
> number will work:
>
> http://www.cyberciti.biz/tips/delete-remove-files-with-inode-number.html
>
To OP:
Use find to do the whole job:
1. cd into the directory in which the file with the bad name is lodged,
2. find . -maxdepth 1 -ls
3. look at output an
On Wed, 2 May 2012 07:04:55 +0200, Jochen wrote in message
<20120502050455.ga25...@well-adjusted.de>:
> Dennis Wicks:
> > Greetings;
> >
> > I have a file that looks like the following in an ls list;
> >
> > -? ? ?? ?? Inbox.msf
> >
> > I can't do anythi
On Wed, May 2, 2012 at 5:16 AM, Andrei POPESCU wrote:
> On Ma, 01 mai 12, 19:15:19, Indulekha wrote:
>>
>> It's always wise to alias "rm" to "rm -i" in your shell.
>> Also learned the hard way, when the combination of a killer
>> headache and time pressure caused me to delete a bunch of
>> things
On Ma, 01 mai 12, 19:15:19, Indulekha wrote:
>
> It's always wise to alias "rm" to "rm -i" in your shell.
> Also learned the hard way, when the combination of a killer
> headache and time pressure caused me to delete a bunch of
> things years ago...
I used to think so as well, but consider situ
Dennis Wicks:
> Greetings;
>
> I have a file that looks like the following in an ls list;
>
> -? ? ?? ?? Inbox.msf
>
> I can't do anything with it. Can't mv, rm, cp, or anything else I
> have thought of to get rid of it or write over it.
>
> Any ideas how
On Tue, May 01, 2012 at 06:20:11PM -0500, Dennis Wicks wrote:
> Greetings;
>
> I have a file that looks like the following in an ls list;
>
> -? ? ?? ?? Inbox.msf
>
> I can't do anything with it. Can't mv, rm, cp, or anything else I
> have thought of to g
--- On Tue, 5/1/12, Dennis Wicks wrote:
> From: Dennis Wicks
> Subject: How do I remove a bad file??
> To: debian-user@lists.debian.org
> Date: Tuesday, May 1, 2012, 6:20 PM
> Greetings;
>
> I have a file that looks like the fo
On Tue, May 01, 2012 at 04:46:19PM -0700, Dan Hitt wrote:
> Handle this with great care!!
>
> If you can remove it in the gui, do so.
>
> That would be safest.
>
> If you cannot, then look up the man page on rm, and make
> sure that the -i flag works.
>
> -i stands for inquire, and should ask y
Handle this with great care!!
If you can remove it in the gui, do so.
That would be safest.
If you cannot, then look up the man page on rm, and make
sure that the -i flag works.
-i stands for inquire, and should ask you for each file that
it wants to remove whether to remove it or not.
When yo
Greetings;
I have a file that looks like the following in an ls list;
-? ? ?? ?? Inbox.msf
I can't do anything with it. Can't mv, rm, cp, or anything
else I have thought of to get rid of it or write over it.
Any ideas how I can get this thing out of my
the
>following error.
>
> bootlogd: ioctl (/dev/ttyzf, TIOCCONS): Bad file descriptor
Looks like something is not well with /dev/ttyzf. Is it present?
Are you using 'udev' ?
>I pressume that I need to examine the setup file for bootlogd
bootlogd doesn't have a config
Hi,
I'm running unstable on both my laptop and desktop, and a few days ago
when attempting to install xserver-svga, I got a 'bad file descriptor'
error from dpkg. Oddly enough, my desktop machine continues on, but
on the laptop, dpkg hangs until I hit ^C and abort. Worse yet,
On Sun, 09 Dec 2001, Eric G. Miller wrote:
> > home:~ #df 1>&-
> > df: write error: Bad file descriptor
> > Is it a bug?
> > ">&-" should be compatible with ">/dev/null", right?
Well, no. AFAIK, >&- means to *close* the s
On Mon, 10 Dec 2001 14:42:15 +0800, Patrick Hsieh <[EMAIL PROTECTED]> wrote:
> Hello,
> home:~ #df 1>&-
> df: write error: Bad file descriptor
>
> Is it a bug?
> ">&-" should be compatible with ">/dev/null", right?
If it is, it mu
Hello,
home:~ #df 1>&-
df: write error: Bad file descriptor
Is it a bug?
">&-" should be compatible with ">/dev/null", right?
--
Patrick Hsieh <[EMAIL PROTECTED]>
On Sunday 14 October 2001 05:26, Robert Waldner wrote:
> On Sat, 13 Oct 2001 22:18:55 PDT, Kevin writes:
> >its got nothing to do with the attribs or the perms
> >
> >lsattr: Inappropriate ioctl for device While reading flags on
> > ./guide.it.html
> >
> >and i cant fsck it because im not local and
On Sat, 13 Oct 2001 22:18:55 PDT, Kevin writes:
>its got nothing to do with the attribs or the perms
>
>lsattr: Inappropriate ioctl for device While reading flags on ./guide.it.html
>
>and i cant fsck it because im not local and cant go to single user.
>oh well, thanks for the help
Maybe you don
its got nothing to do with the attribs or the perms
lsattr: Inappropriate ioctl for device While reading flags on ./guide.it.html
and i cant fsck it because im not local and cant go to single user.
oh well, thanks for the help
> On Sat, Oct 13, 2001 at 08:07:12PM -0700, Kevin wrote:
> > [EMAIL
On Sat, Oct 13, 2001 at 08:07:12PM -0700, Kevin wrote:
> [EMAIL PROTECTED]:/usr/share/doc/apt# chmod 644 guide.it.html
> chmod: changing permissions of `guide.it.html': Operation not permitted
try lsattr guide.it.html, guess the 'i' attribute is set (immutable)
chattr -i guide.it.html should fix it
[EMAIL PROTECTED]:/usr/share/doc/apt# chmod 644 guide.it.html
chmod: changing permissions of `guide.it.html': Operation not permitted
>
> >> On Sat, 13 Oct 2001 12:01:40 PDT, Kevin writes:
> >> >it looks like the filesystem is screwed up
> >> >
> >> >is there a way i can remove/fix this file remot
>> On Sat, 13 Oct 2001 12:01:40 PDT, Kevin writes:
>> >it looks like the filesystem is screwed up
>> >
>> >is there a way i can remove/fix this file remotely (ie no init 1)
>> >
>> >?-wS--x-w- 25830 3373684167 3802483123 14067798681382885448 Sep 2 1905 g
>uid
>> >e.it.html
>>
>> Long shot: Hav
[EMAIL PROTECTED]:/usr/share/doc/apt# cat /dev/null >guide.it.html
su: guide.it.html: Permission denied
and as for just trying to rm it, i already showed i cant do that
> On Sat, 13 Oct 2001 12:01:40 PDT, Kevin writes:
> >it looks like the filesystem is screwed up
> >
> >is there a way i can remo
On Sat, 13 Oct 2001 12:01:40 PDT, Kevin writes:
>it looks like the filesystem is screwed up
>
>is there a way i can remove/fix this file remotely (ie no init 1)
>
>?-wS--x-w- 25830 3373684167 3802483123 14067798681382885448 Sep 2 1905 guid
>e.it.html
Long shot: Have you tried `cat /dev/null >g
Kevin([EMAIL PROTECTED]) is reported to have said:
> it looks like the filesystem is screwed up
>
> is there a way i can remove/fix this file remotely (ie no init 1)
>
> ?-wS--x-w- 25830 3373684167 3802483123 14067798681382885448 Sep 2 1905
> guide.it.html
>
> [EMAIL PROTECTED]:/usr/share/do
it looks like the filesystem is screwed up
is there a way i can remove/fix this file remotely (ie no init 1)
?-wS--x-w- 25830 3373684167 3802483123 14067798681382885448 Sep 2 1905
guide.it.html
[EMAIL PROTECTED]:/usr/share/doc/apt# rm guide.it.html
rm: cannot unlink `guide.it.html': Operatio
On Tue, 13 Feb 2001 [EMAIL PROTECTED] wrote:
>...
> # ifconfig lo 127.0.0.1
> SIOCSIFADDR: Bad file descriptor
> lo: unknown interface: Bad file descriptor
>
> # ifconfig lo down
> lo: unknown interface: Bad file descriptor
>
> Any help is appreciated.
This has nothing
back to 2.4.0, pulled out everything extra possible,
and I'm still getting the error. Interfaces appear in an "ifconfig -a"
and in /proc/net/dev, can be shown by "ifconfig INTERFACE", but any
attempt to change a setting, like IP address and I get:
# ifconfig lo 127.0.0.1
SI
change tty /dev/tty1: Bad file descriptor
Anyone know how I can get around this? If I press ctrl-alt-del I get a
maintenance prompt and it asks for the root password. I get in but I
can`t do anything says no job control processes. I desperately need to
get my machine back running. Any help would be
; for user 'root'
Unable to change tty /dev/tty1: Bad file number
I can't figure out what's going wrong. If I Ctrl-Alt-Del, it won't
reboot, but instead asks me for a root password like it's trying to
go to single-user mode (this may be a debian feature, I don't
Nelson Posse Lago writes:
>
> Hi,
>
> I've setup debian on a friend's box and syslog puts the message:
>
> syslog: don't-remember-what Bad File Number
>
> on /var/log/messages, then it says "last message repeated 437835 times"
> several
Hi,
I've setup debian on a friend's box and syslog puts the message:
syslog: don't-remember-what Bad File Number
on /var/log/messages, then it says "last message repeated 437835 times"
several times and keeps the load average at around 1. Anyone knows what
is this?
70 matches
Mail list logo
