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
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 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
32 matches
Mail list logo
