date:20180825

El 25 de agosto de 2018, 9:00, Pablo Álvarez Córdoba <
pabloalvarezcord...@protonmail.ch> escribió:

> He hecho una prueba en local, por si había algún fallo.
> Me funciona correctamente.
> Lo que pasa es que apache al hacer la petición al servicio que corre en el
> puerto 8069, pone en los header:
>
> Host: miweb.com
> Imagino que tienes configurado en odoo que el hostname es la ip, por eso
> te redirige ahí.
> Prueba a configurar correctamente odoo, o a cambiar ProxyPreserveHost a
> Off.
>
> Estás poniendo  ProxyPass / http://localhost:8069/ así que si desactivas
> ProxyPreserveHost apache enviará:
> Host: localhost:8069
> Debes mirar qué hostname se supone que espera odoo. Quizá una solución sea
> desactivar ProxyPreserveHost y poner ProxyPass / http://IP:8069/ ya que
> parece que odoo espera que accedas mediante la dirección IP.
> Si necesitas que odoo sepa que el hostname es miweb.com, entonces activa
> ProxyPreserveHost y configura en odoo el hostname, y ponle miweb.com.
>
> Si ejecutas curl miweb.com --dump-header - deberías ver que te está
> mandando un redirect. Si ejecutas curl ipdeodoo:8069 --dump-header - no
> debería darte un redirect. Si ejecutas curl -v ipdeodoo:8069 --header
> "Host: miweb.com" debería volverte a dar un redirect, ya que espera que
> host, sea la ip.
>

Pablo aca cuando me decis "Si necesitas que odoo sepa que el hostname es
miweb.com, entonces activa ProxyPreserveHost y configura en odoo el
hostname, y ponle miweb.com."
Es que en el /etc/hosts ponga la ip publica del servidor o sea ippublica
miweb.com?

Saludos

Re: Problemas con apache

El 25 de agosto de 2018, 11:58, Fernando Romero 
escribió:

>
>
> El 25 de agosto de 2018, 9:13, Fernando Romero 
> escribió:
>
>>
>>
>> El sáb., ago. 25, 2018 9:00, Pablo Álvarez Córdoba <
>> pabloalvarezcord...@protonmail.ch> escribió:
>>
>>> He hecho una prueba en local, por si había algún fallo.
>>> Me funciona correctamente.
>>> Lo que pasa es que apache al hacer la petición al servicio que corre en
>>> el puerto 8069, pone en los header:
>>>
>>> Host: miweb.com
>>> Imagino que tienes configurado en odoo que el hostname es la ip, por eso
>>> te redirige ahí.
>>> Prueba a configurar correctamente odoo, o a cambiar ProxyPreserveHost a
>>> Off.
>>>
>>> Estás poniendo  ProxyPass / http://localhost:8069/ así que si
>>> desactivas ProxyPreserveHost apache enviará:
>>> Host: localhost:8069
>>> Debes mirar qué hostname se supone que espera odoo. Quizá una solución
>>> sea desactivar ProxyPreserveHost y poner ProxyPass / http://IP:8069/ ya
>>> que parece que odoo espera que accedas mediante la dirección IP.
>>> Si necesitas que odoo sepa que el hostname es miweb.com, entonces
>>> activa ProxyPreserveHost y configura en odoo el hostname, y ponle
>>> miweb.com.
>>>
>>> Si ejecutas curl miweb.com --dump-header - deberías ver que te está
>>> mandando un redirect. Si ejecutas curl ipdeodoo:8069 --dump-header - no
>>> debería darte un redirect. Si ejecutas curl -v ipdeodoo:8069 --header
>>> "Host: miweb.com" debería volverte a dar un redirect, ya que espera que
>>> host, sea la ip.
>>>
>>
>> Pablo muchas gracias por tu respuesta, en cuanto pueda lo pruebo y te
>> cuento.
>>
>>
>> Saludos
>>
>
> Reinicié el servidor odoo y funciono, muchas gracias!
>
> Saludos
>
>
Retomo el tema que parecía solucionado y se volvió atrás.
Lo único que hice fue modificar un modulo del erp (odoo) y volvió a lo de
antes a mostrarme la ip y no el nombre de la web

http://x.x.x.x:8069/web/database/selector
 y no

miweb.com/web/database/selector.

Si escribo el nombre me trae la pagina como digo mas arriba pero me deja
mostrando la ip y no el nombre.
No se que mas tocar en el apache, alguien tuvo este problema?

Saludos y gracias

Re: The Internet locks up Buster

2018-08-25 Thread Borden Rhodes

> I feel like we are missing a trick here. Even with a relatively slow I/O
> device (I was faintly amused to see SSD in the list of relatively slow
> devices, if SSD is slow what is fast?) it should eventually catch up
> UNLESS something is generating an insane amount of I/O over a sustained
> period. Just browsing the web shouldn't do that unless RAM is very
> tight, and the O/P indicated they have lots of RAM.

> So, I think the O/P should look into what is causing all the I/O in the
> first place, and why that I/O is sustained even when most of the
> processes on the system are blocked. Something isn't right there. The
> usual suspect would be swapping but again the O/P said they have
> "large-capacity RAM" and were just browsing the web with or without
> LibreOffice open -- this shouldn't trigger swapping.

Introducing swap reduced lockups because OOM situations decreased.
Firefox is still incredibly broken. Even simple websites lock up my
computer. But most other programs outside of Steam are OK. So I just
use Chromium right now and the system seems relatively stable.

My research suggests that I may have omitted important information in
my initial report. I've installed Buster on btrfs partitions on top of
LVM in an encrypted partition. I read something that seemed to say
that OOM killer waits for writes to complete before killing programs,
but the LVM needs memory to finish writing. So the system locks up and
the hard drive thrashes even though nothing productive gets done. Can
anyone corroborate this?

Another post suggested that browsers need a lot of I/O for caching.
This creates a lot of overhead that could lock up a sub-optimal or
buggy file system configuration. The suggestion is that btrfs isn't
well-suited to many small writes - its trees get imbalanced and
fragmentation increases. This seems consistent with my experience that
I get a lot of hard drive activity on web browsing even with swap off.
Am I on the right track?

So is my encrypted LVM + btrfs at least somewhat to blame? Should I
consider wiping and reloading onto a simpler encrypted file system
setup (either btrfs or ext4)? I like the flexibility that LVM provides
in being able to tune partitions after-the-fact (and I'm not
comfortable with sub-volumes yet), but I'd rather have OOM killer able
to do its job.

Re: question on spamd logging

On Saturday 25 August 2018 14:15:38 Reco wrote:

>   Hi.
>
> On Sat, Aug 25, 2018 at 01:49:53PM -0400, Gene Heskett wrote:
> > > > Aug 25 12:11:35 coyote spamd[4707]: prefork: child states: II
> > > >
> > > > Several hundred a day...
> > >
> > > Try this:
> > >
> > > cat > /etc/rsyslog.d/spamd.conf << EOF
> > >
> > > :syslogtag, startswith, "spamd" /var/log/spamd.log
> > > :syslogtag, startswith, "spamd" stop
> > >
> > > EOF
> > >
> > > service rsyslogd restart
> >
> > no permission
>
> I assumed that I could skip obligatory 'please assume root privileges
> before making systemwide changes'. Apparently I was wrong, but …
>
> > so I cd to e/rs.d sudo -i and made this file
> >
> > :syslogtag, startswith, "spamd" /var/log/spamd.log
> > :syslogtag, startswith, "spamd" stop
>
> … since things worked out themselves, we now have this:
> > And had to do the restart as root, which logged this:
> > Aug 25 13:34:45 coyote rsyslogd: [origin software="rsyslogd"
> > swVersion="7.6.3" x-pid="3079" x-info="http://www.rsyslog.com;]
> > exiting on signal 15.
> > Aug 25 13:34:45 coyote rsyslogd: [origin software="rsyslogd"
> > swVersion="7.6.3" x-pid="23099" x-info="http://www.rsyslog.com;]
> > start
>
> These two are you usual rsyslogd restart. Nothing to see here.
>
> > Aug 25 13:34:45 coyote rsyslogd-3000: unknown priority name ""
> >
> > No clue what that error might be, you?
>
> But this one is sure cryptic. Even if one takes [1] into the account.
> It's been awhile since I've tinkered with wheezy's rsyslogd, try
>
> replacing "stop" with "~". I.e. replace:
> :syslogtag, startswith, "spamd" stop
>
> with:
> :syslogtag, startswith, "spamd" ~
> :
> > Thanks Reco.
>
> You're welcome.
>
> > > Consider adding logrotate configuration file for the new
> > > /var/log/spamd.log.
> > >
> > > And, before you ask, documentation for rsyslogd lives in
> > > "rsyslog-doc" package.
> >
> > Synaptic says its installed, but its not on /usr/share?
>
> It should be /usr/share/doc/rsyslogd-doc.
> I made a habit doing 'dpkg -L …' on newly installed packages.
>
> > Ahh, found it but no mention of that exact syntax of :syslogtag
>
> To put it simply, it's that thing that follows hostname in your
> typical syslog entry. Usually comes in format
> "process_name[process_pid]". In this case it's "spamd[4707]".
>
Ahh, so. Thanks.
> [1] https://www.rsyslog.com/?s=error+3000
>
Generic error, a placeholder IOW. Might be the stop at that because its 
running as a daemon and never shuts down except while rebooting.

> Reco

Back from the radio station now.  Gawd I hate intermittants that fix 
themselves 15 minutes after I've taken the obvious failure apart, 
cleaned all the contacts and it works when I put it back together, then 
drops out 30 minutes later for 20 minutes, and then comes back for the 
rest of the day. But I am a bit smarter for the next time it dies. I'll 
know where to put a couple scope probes next time, just as soon as I can 
get my scope out of the truck and get it powered up.

Thanks Reco.


-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page

Re: mailing list vs "the futur"

2018-08-25 Thread John Hasler

David writes:
> Or are you talking about some type of "shared channel" of which I have
> no knowledge?

Cable providers may have a great many customers on a single cable with
large (but limited) bandwidth.  Some rural providers may have limited
backhaul bandwidth.  They make promises to customers based on optimistic
estimates of peak usage.
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA

Re: mailing list vs "the futur"

2018-08-25 Thread David Wright

On Fri 24 Aug 2018 at 19:16:35 (-0500), John Hasler wrote:
> I wrote:
> > For marketing reasons they like to advertise very high bandwidth, beyond
> > what they can actually support on shared channels, and then block
> > potentially high-bandwidth services that most of their customers will
> > never use and therefor never miss.
> 
> David writes:
> > I thought their concern was usage, not bandwidth (ie speed).
> 
> What sort of providers?  Those with shared channels need to worry about
> bandwidth.

Sorry, but I was was looking at this from the point of view of we
consumers rather than the ISPs. The OP started the discussion, I
think, with a pitch to persuade us to prefer channels other than
email to follow mailing lists. Some have said that using newsgroups
works fine for them. The only mention of speed, bandwidth and usage
I've seen was the person who downloaded the Kernel Development index,
and that complaint was about its size, not the speed at which it was
delivered. I assume the index gets cached somewhere on the user's
machine.

I can understand that were a mailing list to be delivered via the web
on a free service supported by advertising, the discussion of
bandwidth would be highly significant, particularly for those on
dial-up.

Or are you talking about some type of "shared channel" of which I have
no knowledge?

Cheers,
David.

Re: question on spamd logging

Hi.

On Sat, Aug 25, 2018 at 01:49:53PM -0400, Gene Heskett wrote:
> > > Aug 25 12:11:35 coyote spamd[4707]: prefork: child states: II
> > >
> > > Several hundred a day...
> >
> > Try this:
> >
> > cat > /etc/rsyslog.d/spamd.conf << EOF
> >
> > :syslogtag, startswith, "spamd" /var/log/spamd.log
> > :syslogtag, startswith, "spamd" stop
> >
> > EOF
> >
> > service rsyslogd restart
> >
> no permission

I assumed that I could skip obligatory 'please assume root privileges
before making systemwide changes'. Apparently I was wrong, but …

> so I cd to e/rs.d sudo -i and made this file
> :syslogtag, startswith, "spamd" /var/log/spamd.log
> :syslogtag, startswith, "spamd" stop

… since things worked out themselves, we now have this:

> And had to do the restart as root, which logged this:
> Aug 25 13:34:45 coyote rsyslogd: [origin software="rsyslogd" 
> swVersion="7.6.3" x-pid="3079" x-info="http://www.rsyslog.com;] exiting 
> on signal 15.
> Aug 25 13:34:45 coyote rsyslogd: [origin software="rsyslogd" 
> swVersion="7.6.3" x-pid="23099" x-info="http://www.rsyslog.com;] start

These two are you usual rsyslogd restart. Nothing to see here.

> Aug 25 13:34:45 coyote rsyslogd-3000: unknown priority name ""
> 
> No clue what that error might be, you?

But this one is sure cryptic. Even if one takes [1] into the account.
It's been awhile since I've tinkered with wheezy's rsyslogd, try
replacing "stop" with "~". I.e. replace:

:syslogtag, startswith, "spamd" stop

with:

:syslogtag, startswith, "spamd" ~

> Thanks Reco.

You're welcome.

> > Consider adding logrotate configuration file for the new
> > /var/log/spamd.log.
> >
> > And, before you ask, documentation for rsyslogd lives in "rsyslog-doc"
> > package.
> 
> Synaptic says its installed, but its not on /usr/share?

It should be /usr/share/doc/rsyslogd-doc.
I made a habit doing 'dpkg -L …' on newly installed packages.

> Ahh, found it but no mention of that exact syntax of :syslogtag

To put it simply, it's that thing that follows hostname in your typical
syslog entry. Usually comes in format "process_name[process_pid]".
In this case it's "spamd[4707]".

[1] https://www.rsyslog.com/?s=error+3000

Reco

Re: foutmeldingen tijdens apt update en apt upgrade

2018-08-25 Thread Frank Voncken

Gijs Hillenius schreef op za 25-08-2018 om 14:45 [+0200]:
> [...]
> 
> >    dpkg: waarschuwing: 'ldconfig' niet gevonden in PATH of niet
> >    uitvoerbaar
> >    dpkg: waarschuwing: 'start-stop-daemon' niet gevonden in PATH of
> >    niet uitvoerbaar
> >    dpkg: fout: 2 verwachte programma's niet gevonden in PATH of
> > niet
> >    uitvoerbaar
> >    NOOT: PATH van root zou gewoonlijk /usr/local/sbin, /usr/sbin en
> >    /sbin moeten bevatten
> >    E: Sub-process /usr/bin/dpkg returned an error code (2)
> >    root@oudelaptop:/home/familie# 
> > 
> > Het blijkt een bekend probleem te zijn gezien de vele meldingen
> > hierover op het internet. Gelukkig vond ik een eenvoudige
> > oplossing: ik
> > checkte de inhoud van PATH via commando #echo $PATH. Daaruit bleek
> > dat
> > /sbin ontbrak. Ik heb het toegevoegd middels commando # export
> > PATH="$PATH:/sbin". Ik kon vervolgens probleemloos #apt upgrade
> > uitvoeren.
> 
> 
> Er is een nieuwe su, in util-linux, en die denkt anders over PATH dan
> de
> vorige su van Debian.
> 
> Ik had het idee dat men vind dat je "su -" of "su -l" moet gebruiken
> in
> plaats van "su". Die - zorgt ervoor dat je PATH onderdelen blijven
> zoals
> je dat voorheen gewend bent.
> 
> zie discussie hier:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833256#90

Dank je wel voor de leerzame info!

Re: question on spamd logging

On Saturday 25 August 2018 13:08:29 Reco wrote:

>   Hi.
>
> On Sat, Aug 25, 2018 at 12:16:49PM -0400, Gene Heskett wrote:
> > On Saturday 25 August 2018 12:12:09 Reco wrote:
> > >   Hi.
> > >
> > > On Sat, Aug 25, 2018 at 11:27:32AM -0400, Gene Heskett wrote:
> > > > This is expanding the syslog to the point of drowning out any
> > > > real actionable messages.
> > > >
> > > > I think it used to have a log of its own. How, it this continues
> > > > once stretch is up and running, can we put those spamd messages
> > > > back into spamassassin's own log file? Seems like the logical
> > > > place for them.
> > >
> > > It's definitely possible with rsyslog's filtering feature.
> > > Can you provide a sample of the records that annoy you?
> > >
> > > Reco
> >
> > Aug 25 12:10:01 coyote /USR/SBIN/CRON[20245]: (www-data) CMD ([ -x
> > /usr/share/awstats/tools/update.sh ] &&
> > /usr/share/awstats/tools/update.sh) Aug 25 12:11:33 coyote
> > spamd[4854]: spamd: connection from localhost [127.0.0.1]:43518 to
> > port 783, fd 5 Aug 25 12:11:33 coyote spamd[4854]: spamd: setuid to
> > gene succeeded Aug 25 12:11:33 coyote spamd[4854]: spamd: processing
> > message <20180825161027.eaq2xy65oiar6...@p5k.home> aka
> >  for gene:1000 Aug 25 12:11:34
> > coyote spamd[4854]: spamd: clean message (1.6/5.1) for gene:1000 in
> > 1.1 seconds, 10538 bytes. Aug 25 12:11:34 coyote spamd[4854]: spamd:
> > result: . 1 -
> > BAYES_50,HEADER_FROM_DIFFERENT_DOMAINS,RDNS_NONE,T_DKIM_INVALID
> > scantime=1.1,size=10538,user=gene,uid=1000,required_score=5.1,rhost=
> >localhost,raddr=127.0.0.1,rport=43518,mid=<20180825161027.eaq2xy65oia
> >r6...@p5k.home>,rmid=,bayes=0.50
> >,autolearn=no autolearn_force=no
> > Aug 25 12:11:35 coyote spamd[4707]: prefork: child states: II
> >
> > Several hundred a day...
>
> Try this:
>
> cat > /etc/rsyslog.d/spamd.conf << EOF
>
> :syslogtag, startswith, "spamd" /var/log/spamd.log
> :syslogtag, startswith, "spamd" stop
>
> EOF
>
> service rsyslogd restart
>
> Consider adding logrotate configuration file for the new
> /var/log/spamd.log.
>
> And, before you ask, documentation for rsyslogd lives in "rsyslog-doc"
> package.
>
> Reco

but it did move the noise to spamd.log.  Thanks a bunch Reco.


-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page

Re: question on spamd logging

On Saturday 25 August 2018 13:08:29 Reco wrote:

>   Hi.
>
> On Sat, Aug 25, 2018 at 12:16:49PM -0400, Gene Heskett wrote:
> > On Saturday 25 August 2018 12:12:09 Reco wrote:
> > >   Hi.
> > >
> > > On Sat, Aug 25, 2018 at 11:27:32AM -0400, Gene Heskett wrote:
> > > > This is expanding the syslog to the point of drowning out any
> > > > real actionable messages.
> > > >
> > > > I think it used to have a log of its own. How, it this continues
> > > > once stretch is up and running, can we put those spamd messages
> > > > back into spamassassin's own log file? Seems like the logical
> > > > place for them.
> > >
> > > It's definitely possible with rsyslog's filtering feature.
> > > Can you provide a sample of the records that annoy you?
> > >
> > > Reco
> >
> > Aug 25 12:10:01 coyote /USR/SBIN/CRON[20245]: (www-data) CMD ([ -x
> > /usr/share/awstats/tools/update.sh ] &&
> > /usr/share/awstats/tools/update.sh) Aug 25 12:11:33 coyote
> > spamd[4854]: spamd: connection from localhost [127.0.0.1]:43518 to
> > port 783, fd 5 Aug 25 12:11:33 coyote spamd[4854]: spamd: setuid to
> > gene succeeded Aug 25 12:11:33 coyote spamd[4854]: spamd: processing
> > message <20180825161027.eaq2xy65oiar6...@p5k.home> aka
> >  for gene:1000 Aug 25 12:11:34
> > coyote spamd[4854]: spamd: clean message (1.6/5.1) for gene:1000 in
> > 1.1 seconds, 10538 bytes. Aug 25 12:11:34 coyote spamd[4854]: spamd:
> > result: . 1 -
> > BAYES_50,HEADER_FROM_DIFFERENT_DOMAINS,RDNS_NONE,T_DKIM_INVALID
> > scantime=1.1,size=10538,user=gene,uid=1000,required_score=5.1,rhost=
> >localhost,raddr=127.0.0.1,rport=43518,mid=<20180825161027.eaq2xy65oia
> >r6...@p5k.home>,rmid=,bayes=0.50
> >,autolearn=no autolearn_force=no
> > Aug 25 12:11:35 coyote spamd[4707]: prefork: child states: II
> >
> > Several hundred a day...
>
> Try this:
>
> cat > /etc/rsyslog.d/spamd.conf << EOF
>
> :syslogtag, startswith, "spamd" /var/log/spamd.log
> :syslogtag, startswith, "spamd" stop
>
> EOF
>
> service rsyslogd restart
>
no permission

so I cd to e/rs.d sudo -i and made this file
:syslogtag, startswith, "spamd" /var/log/spamd.log
:syslogtag, startswith, "spamd" stop

And had to do the restart as root, which logged this:
Aug 25 13:34:45 coyote rsyslogd: [origin software="rsyslogd" 
swVersion="7.6.3" x-pid="3079" x-info="http://www.rsyslog.com;] exiting 
on signal 15.
Aug 25 13:34:45 coyote rsyslogd: [origin software="rsyslogd" 
swVersion="7.6.3" x-pid="23099" x-info="http://www.rsyslog.com;] start
Aug 25 13:34:45 coyote rsyslogd-3000: unknown priority name ""

No clue what that error might be, you?

Thanks Reco.

> Consider adding logrotate configuration file for the new
> /var/log/spamd.log.
>
> And, before you ask, documentation for rsyslogd lives in "rsyslog-doc"
> package.

Synaptic says its installed, but its not on /usr/share?

Ahh, found it but no mention of that exact syntax of :syslogtag
>
> Reco



-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page

Re: question on spamd logging

Hi.

On Sat, Aug 25, 2018 at 12:16:49PM -0400, Gene Heskett wrote:
> On Saturday 25 August 2018 12:12:09 Reco wrote:
> 
> > Hi.
> >
> > On Sat, Aug 25, 2018 at 11:27:32AM -0400, Gene Heskett wrote:
> > > This is expanding the syslog to the point of drowning out any real
> > > actionable messages.
> > >
> > > I think it used to have a log of its own. How, it this continues
> > > once stretch is up and running, can we put those spamd messages back
> > > into spamassassin's own log file? Seems like the logical place for
> > > them.
> >
> > It's definitely possible with rsyslog's filtering feature.
> > Can you provide a sample of the records that annoy you?
> >
> > Reco
> 
> Aug 25 12:10:01 coyote /USR/SBIN/CRON[20245]: (www-data) CMD ([ -x 
> /usr/share/awstats/tools/update.sh ] && /usr/share/awstats/tools/update.sh)
> Aug 25 12:11:33 coyote spamd[4854]: spamd: connection from localhost 
> [127.0.0.1]:43518 to port 783, fd 5
> Aug 25 12:11:33 coyote spamd[4854]: spamd: setuid to gene succeeded
> Aug 25 12:11:33 coyote spamd[4854]: spamd: processing message 
> <20180825161027.eaq2xy65oiar6...@p5k.home> aka 
>  for gene:1000
> Aug 25 12:11:34 coyote spamd[4854]: spamd: clean message (1.6/5.1) for 
> gene:1000 in 1.1 seconds, 10538 bytes.
> Aug 25 12:11:34 coyote spamd[4854]: spamd: result: . 1 - 
> BAYES_50,HEADER_FROM_DIFFERENT_DOMAINS,RDNS_NONE,T_DKIM_INVALID 
> scantime=1.1,size=10538,user=gene,uid=1000,required_score=5.1,rhost=localhost,raddr=127.0.0.1,rport=43518,mid=<20180825161027.eaq2xy65oiar6...@p5k.home>,rmid=,bayes=0.50,autolearn=no
>  
> autolearn_force=no
> Aug 25 12:11:35 coyote spamd[4707]: prefork: child states: II
> 
> Several hundred a day...

Try this:

cat > /etc/rsyslog.d/spamd.conf << EOF
:syslogtag, startswith, "spamd" /var/log/spamd.log
:syslogtag, startswith, "spamd" stop
EOF

service rsyslogd restart

Consider adding logrotate configuration file for the new
/var/log/spamd.log.

And, before you ask, documentation for rsyslogd lives in "rsyslog-doc"
package.

Reco

Re: question on spamd logging

On Saturday 25 August 2018 12:12:09 Reco wrote:

>   Hi.
>
> On Sat, Aug 25, 2018 at 11:27:32AM -0400, Gene Heskett wrote:
> > This is expanding the syslog to the point of drowning out any real
> > actionable messages.
> >
> > I think it used to have a log of its own. How, it this continues
> > once stretch is up and running, can we put those spamd messages back
> > into spamassassin's own log file? Seems like the logical place for
> > them.
>
> It's definitely possible with rsyslog's filtering feature.
> Can you provide a sample of the records that annoy you?
>
> Reco

Aug 25 12:10:01 coyote /USR/SBIN/CRON[20245]: (www-data) CMD ([ -x 
/usr/share/awstats/tools/update.sh ] && /usr/share/awstats/tools/update.sh)
Aug 25 12:11:33 coyote spamd[4854]: spamd: connection from localhost 
[127.0.0.1]:43518 to port 783, fd 5
Aug 25 12:11:33 coyote spamd[4854]: spamd: setuid to gene succeeded
Aug 25 12:11:33 coyote spamd[4854]: spamd: processing message 
<20180825161027.eaq2xy65oiar6...@p5k.home> aka 
 for gene:1000
Aug 25 12:11:34 coyote spamd[4854]: spamd: clean message (1.6/5.1) for 
gene:1000 in 1.1 seconds, 10538 bytes.
Aug 25 12:11:34 coyote spamd[4854]: spamd: result: . 1 - 
BAYES_50,HEADER_FROM_DIFFERENT_DOMAINS,RDNS_NONE,T_DKIM_INVALID 
scantime=1.1,size=10538,user=gene,uid=1000,required_score=5.1,rhost=localhost,raddr=127.0.0.1,rport=43518,mid=<20180825161027.eaq2xy65oiar6...@p5k.home>,rmid=,bayes=0.50,autolearn=no
 
autolearn_force=no
Aug 25 12:11:35 coyote spamd[4707]: prefork: child states: II

Several hundred a day...

Thanks Reco

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page

Re: question on spamd logging

Hi.

On Sat, Aug 25, 2018 at 11:27:32AM -0400, Gene Heskett wrote:
> This is expanding the syslog to the point of drowning out any real 
> actionable messages.
> 
> I think it used to have a log of its own. How, it this continues once 
> stretch is up and running, can we put those spamd messages back into 
> spamassassin's own log file? Seems like the logical place for them.

It's definitely possible with rsyslog's filtering feature.
Can you provide a sample of the records that annoy you?

Reco

Re: Swap priority in Debian

Hi.

On Sat, Aug 25, 2018 at 06:07:01PM +0530, Subhadip Ghosh wrote:
> 
> 
> On Saturday 25 August 2018 04:29 PM, Reco wrote:
> > Hi.
> > 
> > On Sat, Aug 25, 2018 at 09:42:31AM +0530, Subhadip Ghosh wrote:
> > > Hi,
> > > 
> > > I am a Debian testing user. Recently I am experiencing freezing on my 
> > > Debian
> > > system intermittently and during troubleshooting the same, I found out 
> > > that
> > > the I have a swap partition with priority set to -2.
> > Same here with stable.
> > 
> > 
> > > But according to the below manpage:
> > > 
> > > https://manpages.debian.org/stretch/mount/swapon.8.en.html
> > > 
> > > swap priority should be between -1 and 32767.
> > So swapon(8) utility has this restriction. Note that the system call
> > itself - swapon(2) merely interprets swap priority as a signed integer,
> > so any priority number is actually possible (within integer limits of
> > course).
> > 
> > 
> > > I have a swappiness value of 60 but I don't remember seeing the swap
> > > being used at all recently, the used swap is always 0%.
> > A hint. They invented this wonderful thing called sysstat decades ago so
> > you don't have to remember your swap usage, along with other things
> > sysstat gathers.
> > 
> > 
> > > My question is, do you think that the -2 priority is stopping the swap
> > > partition from actually being used and because of that, the system is
> > > getting frozen when the memory usage is high?
> > No, it definitely does not work this way.
> > A swap priority only comes into play once you have multiple instances of
> > swaps. If you have a single swap partition/lv/file, a priority value is
> > meaningless.
> > 
> > A system freezes, on the other hand (did I mention sysstat?), could
> > indicate heavy swapping, barrier writes, kernel bugs (12309, anyone?),
> > oom killer invocations, overheating and many other things.
> > A good starting point would be kernel message log (aka
> > /var/log/kern.log) from the time of this freeze.
> Thanks for the suggestion. I checked the kern.log but did not find any
> suspicious log, in fact no entry from that exact time frame when the last
> freeze happened. Do you have any other suggestions to troubleshoot the
> freezes?

"sar -r ALL -f 25" and "sar -S -f 25" would be the next logical step.
Note that "25" means current date (i.e. 25th of current month).

Should be preceeded by "apt install sysstat", of course.

Reco

question on spamd logging

Greetings all;

32 bit wheezy on 64 bit hardware here, for about 4 or 5 days yet as I 
have stuff to install stretch on a fedex truck someplace between the 
left coast and north central WV.

Ever since the main log being switched from /v/l/messages to /v/l/syslog, 
this syslog is getting spammed by spamd stuff everytime spamd looks at 
an incoming email. Several hundred stanza's of this in a typical day.

This is expanding the syslog to the point of drowning out any real 
actionable messages.

I think it used to have a log of its own. How, it this continues once 
stretch is up and running, can we put those spamd messages back into 
spamassassin's own log file? Seems like the logical place for them.

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page

Re: Problemas con apache

El 25 de agosto de 2018, 9:13, Fernando Romero 
escribió:

>
>
> El sáb., ago. 25, 2018 9:00, Pablo Álvarez Córdoba  protonmail.ch> escribió:
>
>> He hecho una prueba en local, por si había algún fallo.
>> Me funciona correctamente.
>> Lo que pasa es que apache al hacer la petición al servicio que corre en
>> el puerto 8069, pone en los header:
>>
>> Host: miweb.com
>> Imagino que tienes configurado en odoo que el hostname es la ip, por eso
>> te redirige ahí.
>> Prueba a configurar correctamente odoo, o a cambiar ProxyPreserveHost a
>> Off.
>>
>> Estás poniendo  ProxyPass / http://localhost:8069/ así que si desactivas
>> ProxyPreserveHost apache enviará:
>> Host: localhost:8069
>> Debes mirar qué hostname se supone que espera odoo. Quizá una solución
>> sea desactivar ProxyPreserveHost y poner ProxyPass / http://IP:8069/ ya
>> que parece que odoo espera que accedas mediante la dirección IP.
>> Si necesitas que odoo sepa que el hostname es miweb.com, entonces activa
>> ProxyPreserveHost y configura en odoo el hostname, y ponle miweb.com.
>>
>> Si ejecutas curl miweb.com --dump-header - deberías ver que te está
>> mandando un redirect. Si ejecutas curl ipdeodoo:8069 --dump-header - no
>> debería darte un redirect. Si ejecutas curl -v ipdeodoo:8069 --header
>> "Host: miweb.com" debería volverte a dar un redirect, ya que espera que
>> host, sea la ip.
>>
>
> Pablo muchas gracias por tu respuesta, en cuanto pueda lo pruebo y te
> cuento.
>
>
> Saludos
>

Reinicié el servidor odoo y funciono, muchas gracias!

Saludos

Re: mailing list vs "the futur"

2018-08-25 Thread Richard Owlett


On 08/25/2018 07:18 AM, John Hasler wrote:

Richard writes:

I am subscribed to 17 mailing lists and follow 22 USENET groups.


The providers that block NNTP are concerned about binary groups (which
they most likely believe to be the only kind that exist).



Yes. I was just trying to give a data point to give a real use-case 
perspective.

Re: foutmeldingen tijdens apt update en apt upgrade

2018-08-25 Thread Gijs Hillenius



[...]

>dpkg: waarschuwing: 'ldconfig' niet gevonden in PATH of niet
>uitvoerbaar
>dpkg: waarschuwing: 'start-stop-daemon' niet gevonden in PATH of
>niet uitvoerbaar
>dpkg: fout: 2 verwachte programma's niet gevonden in PATH of niet
>uitvoerbaar
>NOOT: PATH van root zou gewoonlijk /usr/local/sbin, /usr/sbin en
>/sbin moeten bevatten
>E: Sub-process /usr/bin/dpkg returned an error code (2)
>root@oudelaptop:/home/familie# 
>
> Het blijkt een bekend probleem te zijn gezien de vele meldingen
> hierover op het internet. Gelukkig vond ik een eenvoudige oplossing: ik
> checkte de inhoud van PATH via commando #echo $PATH. Daaruit bleek dat
> /sbin ontbrak. Ik heb het toegevoegd middels commando # export
> PATH="$PATH:/sbin". Ik kon vervolgens probleemloos #apt upgrade
> uitvoeren.


Er is een nieuwe su, in util-linux, en die denkt anders over PATH dan de
vorige su van Debian.

Ik had het idee dat men vind dat je "su -" of "su -l" moet gebruiken in
plaats van "su". Die - zorgt ervoor dat je PATH onderdelen blijven zoals
je dat voorheen gewend bent.

zie discussie hier:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833256#90

Re: Swap priority in Debian

2018-08-25 Thread Subhadip Ghosh





On Saturday 25 August 2018 04:29 PM, Reco wrote:

Hi.

On Sat, Aug 25, 2018 at 09:42:31AM +0530, Subhadip Ghosh wrote:

Hi,

I am a Debian testing user. Recently I am experiencing freezing on my Debian
system intermittently and during troubleshooting the same, I found out that
the I have a swap partition with priority set to -2.

Same here with stable.



But according to the below manpage:

https://manpages.debian.org/stretch/mount/swapon.8.en.html

swap priority should be between -1 and 32767.

So swapon(8) utility has this restriction. Note that the system call
itself - swapon(2) merely interprets swap priority as a signed integer,
so any priority number is actually possible (within integer limits of
course).



I have a swappiness value of 60 but I don't remember seeing the swap
being used at all recently, the used swap is always 0%.

A hint. They invented this wonderful thing called sysstat decades ago so
you don't have to remember your swap usage, along with other things
sysstat gathers.



My question is, do you think that the -2 priority is stopping the swap
partition from actually being used and because of that, the system is
getting frozen when the memory usage is high?

No, it definitely does not work this way.
A swap priority only comes into play once you have multiple instances of
swaps. If you have a single swap partition/lv/file, a priority value is
meaningless.

A system freezes, on the other hand (did I mention sysstat?), could
indicate heavy swapping, barrier writes, kernel bugs (12309, anyone?),
oom killer invocations, overheating and many other things.
A good starting point would be kernel message log (aka
/var/log/kern.log) from the time of this freeze.
Thanks for the suggestion. I checked the kern.log but did not find any 
suspicious log, in fact no entry from that exact time frame when the 
last freeze happened. Do you have any other suggestions to troubleshoot 
the freezes?

Re: mailing list vs "the futur"

2018-08-25 Thread John Hasler

Richard writes:
> I am subscribed to 17 mailing lists and follow 22 USENET groups.

The providers that block NNTP are concerned about binary groups (which
they most likely believe to be the only kind that exist).
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA

Re: Problemas con apache

El sáb., ago. 25, 2018 9:00, Pablo Álvarez Córdoba <
pabloalvarezcord...@protonmail.ch> escribió:

> He hecho una prueba en local, por si había algún fallo.
> Me funciona correctamente.
> Lo que pasa es que apache al hacer la petición al servicio que corre en el
> puerto 8069, pone en los header:
>
> Host: miweb.com
> Imagino que tienes configurado en odoo que el hostname es la ip, por eso
> te redirige ahí.
> Prueba a configurar correctamente odoo, o a cambiar ProxyPreserveHost a
> Off.
>
> Estás poniendo  ProxyPass / http://localhost:8069/ así que si desactivas
> ProxyPreserveHost apache enviará:
> Host: localhost:8069
> Debes mirar qué hostname se supone que espera odoo. Quizá una solución sea
> desactivar ProxyPreserveHost y poner ProxyPass / http://IP:8069/ ya que
> parece que odoo espera que accedas mediante la dirección IP.
> Si necesitas que odoo sepa que el hostname es miweb.com, entonces activa
> ProxyPreserveHost y configura en odoo el hostname, y ponle miweb.com.
>
> Si ejecutas curl miweb.com --dump-header - deberías ver que te está
> mandando un redirect. Si ejecutas curl ipdeodoo:8069 --dump-header - no
> debería darte un redirect. Si ejecutas curl -v ipdeodoo:8069 --header
> "Host: miweb.com" debería volverte a dar un redirect, ya que espera que
> host, sea la ip.
>

Pablo muchas gracias por tu respuesta, en cuanto pueda lo pruebo y te
cuento.


Saludos

>

Re: Problemas con apache

2018-08-25 Thread Pablo Álvarez Córdoba

He hecho una prueba en local, por si había algún fallo.

Me funciona correctamente.
Lo que pasa es que apache al hacer la petición al servicio que corre en el 
puerto 8069, pone en los header:

Host: miweb.com

Imagino que tienes configurado en odoo que el hostname es la ip, por eso te 
redirige ahí.
Prueba a configurar correctamente odoo, o a cambiar ProxyPreserveHost a Off.

Estás poniendo  ProxyPass / http://localhost:8069/ así que si desactivas 
ProxyPreserveHost apache enviará:
Host: localhost:8069
Debes mirar qué hostname se supone que espera odoo. Quizá una solución sea 
desactivar ProxyPreserveHost y poner ProxyPass / http://IP:8069/ ya que parece 
que odoo espera que accedas mediante la dirección IP.
Si necesitas que odoo sepa que el hostname es miweb.com, entonces activa 
ProxyPreserveHost y configura en odoo el hostname, y ponle miweb.com.

Si ejecutas curl miweb.com --dump-header - deberías ver que te está mandando un 
redirect. Si ejecutas curl ipdeodoo:8069 --dump-header - no debería darte un 
redirect. Si ejecutas curl -v ipdeodoo:8069 --header "Host: miweb.com" debería 
volverte a dar un redirect, ya que espera que host, sea la ip.

Re: Problemas con apache

El sáb., ago. 25, 2018 8:07, Pablo Álvarez Córdoba <
pabloalvarezcord...@protonmail.ch> escribió:

> ¿A qué te referías cuando dijiste lo siguiente?:
>
> La web levanta pero me muestra por ip y no por nombre, la llamo por el
> nombre y abre el sitio pero me queda mostrando http:ip:puerto y no el
> nombre del virtual host.
>
> Escribo la direccion web en el navegador y me levanta la pagina bien pero
donde escribi ejemplo midominio.com me muestra ip:puerto.
No se si me explico bien.

Saludos

>
>

Re: Problemas con apache

2018-08-25 Thread Pablo Álvarez Córdoba

�A qué te referías cuando dijiste lo siguiente?:

> La web levanta pero me muestra por ip y no por nombre, la llamo por el nombre 
> y abre el sitio pero me queda mostrando http:ip:puerto y no el nombre del 
> virtual host.

Re: Re: Swap priority in Debian

2018-08-25 Thread dekkzz78

On 08/25, Rick Thomas wrote:

On Aug 25, 2018, at 1:15 AM, Subhadip Ghosh wrote:

On Saturday 25 August 2018 01:17 PM, Dekks Herton wrote:

Subhadip Ghosh writes:

Hi,

I am a Debian testing user. Recently I am experiencing freezing on my
Debian system intermittently and during troubleshooting the same, I
found out that the I have a swap partition with priority set to
-2. But according to the below manpage:

https://manpages.debian.org/stretch/mount/swapon.8.en.html

swap priority should be between -1 and 32767. I have a swappiness
value of 60 but I don't remember seeing the swap being used at all
recently, the used swap is always 0%.

Whats swapon -s say? do you use zsawp or zram?

FilenameTypeSizeUsedPriority
/dev/sda5 partition8203260 0-2

I am using zswap.

My question is, do you think that the -2 priority is stopping the swap
partition from actually being used and because of that, the system is
getting frozen when the memory usage is high?

No, it's -2 on my stretch box with zswap enabled and it swaps as one
would expect.

My buster box says pretty much the same thing. I’m not using zswap.

FilenameTypeSizeUsed
Priority
/dev/dm-1 partition 104857560
-2

I don’t recall ever having seen it actually use any swap, but that may just be
me not remembering something that didn’t seem important at the time.

Rick

PS: I did manage, just now, to force it to swap a small, but non-zero, amount
by opening lots of tabs in firefox. So it will use a “-2” swap partition if it
has to.
For what it’s worth, I noticed that firefox got kinda slow, but it didn’t
freeze.

I run stretch on a t60p with 2GB of RAM, so i know it swaps as normal. But both I and the OP use zswap which probably sets the prority to -2, FWIW swap space shows 300MB with the
zswap space compressed to 110MB

--
regards.

Dekks Herton

Thinkpad T61 2.0Ghz 2GB WSXGA+

Jabber IM: dekkz...@jabber.hot-chilli.net

signature.asc
Description: PGP signature

Re: Swap priority in Debian

Hi.

On Sat, Aug 25, 2018 at 09:42:31AM +0530, Subhadip Ghosh wrote:
> Hi,
> 
> I am a Debian testing user. Recently I am experiencing freezing on my Debian
> system intermittently and during troubleshooting the same, I found out that
> the I have a swap partition with priority set to -2.

Same here with stable.

> But according to the below manpage:
> 
> https://manpages.debian.org/stretch/mount/swapon.8.en.html
> 
> swap priority should be between -1 and 32767.

So swapon(8) utility has this restriction. Note that the system call
itself - swapon(2) merely interprets swap priority as a signed integer,
so any priority number is actually possible (within integer limits of
course).

> I have a swappiness value of 60 but I don't remember seeing the swap
> being used at all recently, the used swap is always 0%.

A hint. They invented this wonderful thing called sysstat decades ago so
you don't have to remember your swap usage, along with other things
sysstat gathers.

> My question is, do you think that the -2 priority is stopping the swap
> partition from actually being used and because of that, the system is
> getting frozen when the memory usage is high?

No, it definitely does not work this way.
A swap priority only comes into play once you have multiple instances of
swaps. If you have a single swap partition/lv/file, a priority value is
meaningless.

A system freezes, on the other hand (did I mention sysstat?), could
indicate heavy swapping, barrier writes, kernel bugs (12309, anyone?),
oom killer invocations, overheating and many other things.
A good starting point would be kernel message log (aka
/var/log/kern.log) from the time of this freeze.

Reco

Re: mailing list vs "the futur"

2018-08-25 Thread Richard Owlett


On 08/24/2018 06:08 PM, David Wright wrote:

On Fri 24 Aug 2018 at 16:18:40 (-0500), John Hasler wrote:

The Wanderer writes:

If the user chooses a provider which carries those groups, and chooses
to subscribe to one or more of them, then surely that is what that
user is choosing to do with the bandwidth which that user purchases
from that user's provider - and as long as the user's bandwidth limits
are not exceeded, surely it's none of the provider's business what is
transported over that bandwidth.


For marketing reasons they like to advertise very high bandwidth, beyond
what they can actually support on shared channels, and then block
potentially high-bandwidth services that most of their customers will
never use and therefor never miss.


I thought their concern was usage, not bandwidth (ie speed).
360MB is small beer. Downloading a day's House Judiciary Committee
hearing from youtube is around 3-4GB. With TV (all off internet),
we use 15-30GB per day.

Cheers,
David.



As single data point:
I am subscribed to 17 mailing lists and follow 22 USENET groups.
All that plus my routine browsing and downloading system updates from 
Debian keeps me well under my 2GB monthly data cap [typically <1.2GB]

Re: DHCP to static without reboot?

On Saturday 25 August 2018 06:02:20 Gene Heskett wrote:

> On Saturday 25 August 2018 04:20:51 to...@tuxteam.de wrote:
> > On Sat, Aug 25, 2018 at 03:54:32AM -0400, Gene Heskett wrote:
> >
> > [...]
> >
> > > I've experienced that on a armbian install on a rock64, it takes
> > > sometimes 2 or 3 powerdown recycles to make a change in
> > > e-n-i.d/name of interface to stick [...]
> >
> > That sounds a bit like Voodoo. But then, there's Clarke's Third Law.
>
> I looked it up, yes. But the wiki page, a ways down, says:
>
> "seeing and hearing Linotype machines which slowly converted ‘molten
> lead into front pages that required two men to lift them.’  I had to
> chuckle about that because it brought up a memory from my childhood,
1947, damn these ancient fingers.
> 1047 or so. Those old frames were 4" bigger than todays papers, 2
> pages wide, and probably weighed well over 250 lbs loaded and ready
> for the press.
>
> When I was in my early teens, and helping out in the darkroom at our
> local weekly paper, it only took one man to pick up that frame of
> Linotype, carry it out thru the back door to a shed over his press and
> place it on the bed of that press.
>
> his name was John Hines, stood about 6'5" and around 275 lbs, owned
> the paper & job shop and only wore white shirts to work and never once
> did he get any ink in them.
>
> One of the local brickyards supervisor guys was famous for a foul
> mouth, and John and his missus was in a benefit bridge game during an
> Old Settlers Re-union, & this guy came to a position behind Johns
> wife, with every third word being a foul word. John told him to watch
> his mouth, he replied "and what the F--k are you going to do about it?
>
> Johns butt never cleared the folding chair he was sitting on as he
> reached over his wife's head across the table and open handedly
> slapped him cold on the floor. The whole fire hall gave him a hand
> when he stood up, picked him up and laid him gently on a park bench
> just outside the front doors.  End of problem.
>
> Thanks for the trip down memory lane.
>
> > Cheers
> > -- tomás



-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page

Re: DHCP to static without reboot?

On Saturday 25 August 2018 04:20:51 to...@tuxteam.de wrote:

> On Sat, Aug 25, 2018 at 03:54:32AM -0400, Gene Heskett wrote:
>
> [...]
>
> > I've experienced that on a armbian install on a rock64, it takes
> > sometimes 2 or 3 powerdown recycles to make a change in e-n-i.d/name
> > of interface to stick [...]
>
> That sounds a bit like Voodoo. But then, there's Clarke's Third Law.
>
I looked it up, yes. But the wiki page, a ways down, says:

"seeing and hearing Linotype machines which slowly converted ‘molten lead 
into front pages that required two men to lift them.’  I had to chuckle 
about that because it brought up a memory from my childhood, 1047 or so. 
Those old frames were 4" bigger than todays papers, 2 pages wide, and 
probably weighed well over 250 lbs loaded and ready for the press.

When I was in my early teens, and helping out in the darkroom at our 
local weekly paper, it only took one man to pick up that frame of 
Linotype, carry it out thru the back door to a shed over his press and 
place it on the bed of that press.

his name was John Hines, stood about 6'5" and around 275 lbs, owned the 
paper & job shop and only wore white shirts to work and never once did 
he get any ink in them.

One of the local brickyards supervisor guys was famous for a foul mouth, 
and John and his missus was in a benefit bridge game during an Old 
Settlers Re-union, & this guy came to a position behind Johns wife, with 
every third word being a foul word. John told him to watch his mouth, he 
replied "and what the F--k are you going to do about it?

Johns butt never cleared the folding chair he was sitting on as he 
reached over his wife's head across the table and open handedly slapped 
him cold on the floor. The whole fire hall gave him a hand when he stood 
up, picked him up and laid him gently on a park bench just outside the 
front doors.  End of problem.

Thanks for the trip down memory lane.

> Cheers
> -- tomás

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page

Re: Wifi : impossible de me connecter en PEAP/MSCHAPv2 [enfin, ça dépend]

2018-08-25 Thread Christophe Maquaire

Le samedi 25 août 2018 à 10:00 +0200, Christophe Maquaire a écrit :
> 
> et j'ai trouvé la solution là:
> 
> https://lists.debian.org/debian-user/2017/06/msg01045.html
> 

Argh, j'ai lu trop vite, je vois que tu avais déjà essayé cette
solution sans résultat positif.

Désolé,

Christophe

Re: Swap priority in Debian

2018-08-25 Thread Rick Thomas

On Aug 25, 2018, at 1:15 AM, Subhadip Ghosh  wrote:

> 
> On Saturday 25 August 2018 01:17 PM, Dekks Herton wrote:
>> Subhadip Ghosh  writes:
>> 
>>> Hi,
>>> 
>>> I am a Debian testing user. Recently I am experiencing freezing on my
>>> Debian system intermittently and during troubleshooting the same, I
>>> found out that the I have a swap partition with priority set to
>>> -2. But according to the below manpage:
>>> 
>>> https://manpages.debian.org/stretch/mount/swapon.8.en.html
>>> 
>>> swap priority should be between -1 and 32767. I have a swappiness
>>> value of 60 but I don't remember seeing the swap being used at all
>>> recently, the used swap is always 0%.
>> Whats swapon -s say? do you use zsawp or zram?
> FilenameTypeSizeUsedPriority
> /dev/sda5  partition8203260 0-2
> 
> I am using zswap.
>> 
>>> My question is, do you think that the -2 priority is stopping the swap
>>> partition from actually being used and because of that, the system is
>>> getting frozen when the memory usage is high?
>> No, it's -2 on my stretch box with zswap enabled and it swaps as one
>> would expect.
> 

My buster box says pretty much the same thing.  I’m not using zswap.

> Filename  TypeSizeUsed
> Priority
> /dev/dm-1 partition   10485756
> 0   -2

I don’t recall ever having seen it actually use any swap, but that may just be 
me not remembering something that didn’t seem important at the time.

Rick

PS:  I did manage, just now, to force it to swap a small, but non-zero, amount 
by opening lots of tabs in firefox.  So it will use a “-2” swap partition if it 
has to.
For what it’s worth, I noticed that firefox got kinda slow, but it didn’t 
freeze.

Re: DHCP to static without reboot?

On Saturday 25 August 2018 04:20:51 to...@tuxteam.de wrote:

> On Sat, Aug 25, 2018 at 03:54:32AM -0400, Gene Heskett wrote:
>
> [...]
>
> > I've experienced that on a armbian install on a rock64, it takes
> > sometimes 2 or 3 powerdown recycles to make a change in e-n-i.d/name
> > of interface to stick [...]
>
> That sounds a bit like Voodoo. But then, there's Clarke's Third Law.
>
I must admit that Arthers 3rd escapes me ATM. Oldtimers effects more than 
likely as I've read everything he ever wrote.  But I'm sure Murphy has a 
corollary.

> Cheers
> -- tomás



-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page

Re: DHCP to static without reboot?

2018-08-25 Thread tomas

On Sat, Aug 25, 2018 at 03:54:32AM -0400, Gene Heskett wrote:

[...]

> I've experienced that on a armbian install on a rock64, it takes 
> sometimes 2 or 3 powerdown recycles to make a change in e-n-i.d/name of 
> interface to stick [...]

That sounds a bit like Voodoo. But then, there's Clarke's Third Law.

Cheers
-- tomás


signature.asc
Description: Digital signature

Re: Swap priority in Debian

2018-08-25 Thread Subhadip Ghosh




On Saturday 25 August 2018 01:17 PM, Dekks Herton wrote:

Subhadip Ghosh  writes:


Hi,

I am a Debian testing user. Recently I am experiencing freezing on my
Debian system intermittently and during troubleshooting the same, I
found out that the I have a swap partition with priority set to
-2. But according to the below manpage:

https://manpages.debian.org/stretch/mount/swapon.8.en.html

swap priority should be between -1 and 32767. I have a swappiness
value of 60 but I don't remember seeing the swap being used at all
recently, the used swap is always 0%.

Whats swapon -s say? do you use zsawp or zram?

Filename                Type        Size    Used    Priority
/dev/sda5      partition    8203260 0    -2

I am using zswap.



My question is, do you think that the -2 priority is stopping the swap
partition from actually being used and because of that, the system is
getting frozen when the memory usage is high?

No, it's -2 on my stretch box with zswap enabled and it swaps as one
would expect.

Re: Migrer un système debian vers un système de fichiers chiffré luks

2018-08-25 Thread Pascal Hambourg


Le 24/08/2018 à 21:50, dethegeek a écrit :

j'ai prévu un seul vg chiffré, contenant tous mes lv sensibles: rootfs
et home. J'ai initialement prévu que boot soit non chiffré, mais c'est
pas une bone idée. On peut techniquement attaquer ce volume pour y
mettre un keylogger.

La bonne pratique est donc de chiffrer /boot, grub , de ce que je lis,
le gère


Oui. Mais la core image de GRUB (qui demande de taper la passphrase pour 
déchiffrer le volume contenant /boot) reste en clair et donc vulnérable.


Si le but est de se protéger de la divulgation des données en cas de 
perte ou vol de l'ordinateur, alors le chiffrement de /boot n'est pas 
nécessaire, il ne contient pas de donnée sensible.


Si le but est de se protéger contre une intervention illicite sur 
l'ordinateur passée inaperçue, alors le chiffrement quel qu'il soit ne 
suffit pas car il reste toujours une partie en clair pour l'amorçage. Il 
faut y ajouter la vérification de l'intégrité.

Re: Wifi : impossible de me connecter en PEAP/MSCHAPv2 [enfin, ça dépend]

2018-08-25 Thread Christophe Maquaire

Le vendredi 24 août 2018 à 17:39 +0200, David BERCOT a écrit :
> Bonjour,
Bonjour,


> là, impossible de me connecter en Wifi sur mon réseau d'entreprise.
> Le message qui revient le plus souvent est le suivant :
> wlp60s0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice
> (Reason: 3=DEAUTH_LEAVING)


> Bref, auriez-vous une piste ?


Oui, j'ai eu le même souci, me suis inutilement procuré un autre dongle
usb/wifi
et j'ai trouvé la solution là:

https://lists.debian.org/debian-user/2017/06/msg01045.html


> Merci d'avance.

De rien,
> 
> David.

Christophe

Re: DHCP to static without reboot?