Re: ssh

[Alan Taylor]

Hello,

Output from several suggestions:

Permissions (backuppc is the user having problems) :

backuppc@sirius:~$ ls -ld /usr/local/BackupPC
drwxr-xr-x 6 backuppc backuppc 4096 Nov 13 12:12 /usr/local/BackupPC
backuppc@sirius:~$ ls -ld /usr/local/BackupPC/.ssh
drwx-- 2 backuppc backuppc 4096 Nov 13 12:08 /usr/local/BackupPC/.ssh
backuppc@sirius:~$ ls -l /usr/local/BackupPC/.sshtotal 28
-rw--- 1 backuppc backuppc 1790 Nov 13 12:04 authorized_keys
-rw-r- 1 backuppc backuppc 2240 Nov 13 12:02 config
-rw-r--r-- 1 backuppc backuppc  142 Nov 13 12:08 known_hosts
-rw--- 1 backuppc backuppc  484 Nov 13 12:03 sirius_bpc-id_ed25519
-rw-r- 1 backuppc backuppc  126 Nov 13 12:03 sirius_bpc-id_ed25519.pub
-rw--- 1 backuppc backuppc 3479 Nov 13 12:04 sirius_bpc-id_rsa
-rw-r- 1 backuppc backuppc  770 Nov 13 12:04 sirius_bpc-id_rsa.pub
backuppc@sirius:~$
backuppc@sirius:~$ ls -la /etc/ssh
drwxr-xr-x   2 root root   4096 Nov 13 12:04 .
drwxr-xr-x 131 root root  12288 Nov 13 12:05 ..
-rw-r--r--   1 root root 511915 Nov 13 12:02 moduli
-rw-r--r--   1 root root 553122 Aug 21 11:14 moduli.dist
-rw---   1 root root888 Nov 13 12:03 sirius_alan-authorized_keys
-rw-rw   1 root root896 Nov 13 12:04 sirius_bpc-authorized_keys
-rw-r--r--   1 root root   2830 Nov 13 12:02 ssh_config
-rw-r--r--   1 root root   1723 Aug 21 11:14 ssh_config.dist
-rw-r--r--   1 root root   4239 Nov 13 12:02 sshd_config
-rw-r--r--   1 root root   3298 Aug 21 11:14 sshd_config.dist
-rw---   1 root root432 Nov 13 12:03 ssh_host_ed25519_key
-rw-r-   1 root root117 Nov 13 12:03 ssh_host_ed25519_key.pub
-rw---   1 root root   3243 Nov 13 12:03 ssh_host_rsa_key
-rw-r-   1 root root761 Nov 13 12:03 ssh_host_rsa_key.pub
backuppc@sirius:~$
These permissions are identical to the user that works.

Output from David's troubleshooting :

As backuppc (problem user):

backuppc@sirius:~$ whoami
backuppc
backuppc@sirius:~$ hostname
sirius
backuppc@sirius:~$ cat /etc/debian_version
9.6
backuppc@sirius:~$ uname -a
Linux sirius 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64
GNU/Linux
backuppc@sirius:~$ dpkg-query -W openssh-client
openssh-client1:7.4p1-10+deb9u4

backuppc@sirius:~$ ls -aFl /usr/local/BackupPC/.ssh
total 36
drwx-- 2 backuppc backuppc 4096 Nov 13 12:08 ./
drwxr-xr-x 6 backuppc backuppc 4096 Nov 13 12:12 ../
-rw--- 1 backuppc backuppc 1790 Nov 13 12:04 authorized_keys
-rw-r- 1 backuppc backuppc 2240 Nov 13 12:02 config
-rw-r--r-- 1 backuppc backuppc  142 Nov 13 12:08 known_hosts
-rw--- 1 backuppc backuppc  484 Nov 13 12:03 sirius_bpc-id_ed25519
-rw-r- 1 backuppc backuppc  126 Nov 13 12:03 sirius_bpc-id_ed25519.pub
-rw--- 1 backuppc backuppc 3479 Nov 13 12:04 sirius_bpc-id_rsa
-rw-r- 1 backuppc backuppc  770 Nov 13 12:04 sirius_bpc-id_rsa.pub

backuppc@sirius:~$ ssh -v sirius
OpenSSH_7.4p1 Debian-10+deb9u4, OpenSSL 1.0.2l  25 May 2017
debug1: Reading configuration data /usr/local/BackupPC/.ssh/config
debug1: /usr/local/BackupPC/.ssh/config line 16: Applying options for sirius
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: /etc/ssh/ssh_config line 69: Deprecated option "useroaming"
debug1: Connecting to 192.168.8.3 [192.168.8.3] port 50400.
debug1: Connection established.
debug1: identity file /usr/local/BackupPC/.ssh/sirius_bpc-id_ed25519 type 4
debug1: key_load_public: No such file or directory
debug1: identity file /usr/local/BackupPC/.ssh/sirius_bpc-id_ed25519-cert
type -1
debug1: identity file /usr/local/BackupPC/.ssh/sirius_bpc-id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /usr/local/BackupPC/.ssh/sirius_bpc-id_rsa-cert type
-1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.4p1 Debian-10+deb9u4
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4p1
Debian-10+deb9u4
debug1: match: OpenSSH_7.4p1 Debian-10+deb9u4 pat OpenSSH* compat 0x0400
debug1: Authenticating to 192.168.8.3:50400 as 'backuppc'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha...@libssh.org
debug1: kex: host key algorithm: ssh-ed25519
debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC:
 compression: none
debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC:
 compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ssh-ed25519
SHA256:Qmmw9Hw9F68Lv9vTJTHpbJtwOzxUxod4FFAnA16D5bk
debug1: Host '[192.168.8.3]:50400' is known and matches the ED25519 host
key.
debug1: Found key in /usr/local/BackupPC/.ssh/known_hosts:1
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey after 134217728 

Re: Archiving content of a directory on a DVD-R.

[peter]

*   From: Greg Wooledge 
*   Date: Mon, 12 Nov 2018 17:14:13 -0500
> Just put all the commands in one script, for example:
> 
> #!/bin/sh
> backup1 &&
> backup2 &&
> backup3

I was afraid you meant that.  =8~)  My three scripts are executed 
interactively. To my knowledge there can be only one script in a file.  
=8~|  By defining chell functions, all three are in .bashrc.  =8~)

> Here's the backup script I use at home, ...

OK, my first stage follows.  ~/MY/ is an SD card.  This Backup is 
executed when I finish editing something or finish enough editing that 
I wouldn't want to retype it after the flash store fails.  It merely 
syncs from ~/MY/ into ~/MY0.Bak or, if executed with any parameter, to 
~/MY1.Bak.  Then it reports the size of MailMessages and the current size 
of the backup.  Subdirectories, logs, voice messages, installer archives 
and similar non-essential data are excluded.  Definitely more 
primitive than your backup.  Comments welcome of course.

The further two functions put the backup on a DVD-R.  Done once per 
week or less depending on competing "essential" work, fatigue & etc.  Can 
discuss these stages 2 and 3 later.

Thanks, ... Peter E.


Backup() { \
 if [ $# -gt 1 ]; then
   echo "Too many arguments.";
 else
   echo "0 or 1 arguments are OK.";
   if [ $# -eq 0 ]; then
 echo "0 arguments is OK.";
 destination=~/MY0.Bak;
 echo "destination is $destination.";
   else
 echo "1 argument is OK.";
 destination=~/MY1.Bak;
 echo "destination is $destination.";
   fi;
 echo "Executing rsync.";
 rsync \
  --exclude "*/" \
  --exclude='AOS*' \
  --exclude='Trap*' \
  --exclude='*.WAV' \
  --exclude='.aoshome' \
  --exclude "lost+found" \
  --exclude='*.Bak' \
  --exclude='*.bundle' \
  --exclude='*.iso' \
  --exclude='*.mp3' \
  --exclude='*.mp4' \
  --exclude='pe' \
  --exclude='*.sig' \
  --exclude='*.webm' \
  --exclude='*.zd' \
  --exclude='*.zip' \
  --exclude='*Libre*' \
  --exclude='*Linux*' \
  --exclude='Configuration.XML' \
  --exclude='Oberon*Fnt' \
  --exclude='Oberon.Text' \
  -auv /home/peter/MY/* $destination ;
 /bin/ls -ld ~/MY/MailMessages;
 printf "du -s $destination gives ";
 du -s $destination;
  fi;
}

-- 
Message composed and transmitted by software designed to avoid the 
need, overhead and vulnerability of antivirus software.

123456789 123456789 123456789 123456789 123456789 123456789 123456789
Tel: +1 360 639 0202  +1 
http://easthope.ca/Peter.html  Bcc: peter at easthope. ca

Re: ssh

[David Christensen]

On 11/12/18 5:49 AM, Alan Taylor wrote:

Greetings,


Hi.  :-)



I have an ssh problem - one user can use it successfully, another cannot. I 
have checked and rechecked permissions until I am blue in the face …
At the moment just trying to ssh into the same machine I am on for the problem 
user (the other user can ssh successfully, both to the console machine and 
outwards to others).
Agent problem ? The successful user was setup in the installation, the problem 
user was added at the command line after initial setup.


Trouble-shooting can be tedious...



Log output follows, appears to fail after the preauth stage …

Any suggestions gratefully accepted

root@sirius/etc/ssh # journalctl | grep sshd | grep "Nov 12 13:45"




I would enter the following commands into the indicated accounts and 
computers, substituting place holders with actual values (USERNAME, 
SSH_CLIENT, SSH_SERVER).  If you still don't see it, cut and paste your 
console sessions into a reply:


1.  As the user having problems on the computer having problems:

$ whoami

$ hostname

$ cat /etc/debian_version

$ uname -a

$ dpkg-query -W openssh-client

$ ls -aFl /home/USERNAME/.ssh

$ ssh -v SSH_SERVER

2.  As root on the SSH server:

# hostname

# cat /etc/debian_version

# uname -a

# dpkg-query -W openssh-server

# ls -aFl /home/USERNAME/.ssh

# grep USERNAME@SSH_CLIENT /home/USERNAME/.ssh/authorized_keys

# tail /var/log/auth.log


David

Re: ssh

[Alan Taylor]

If of any help, this is the complete journal log associated with a rejected
logon event:

Nov 13 12:28:07 sirius sshd[789]: debug3: fd 4 is not O_NONBLOCK
Nov 13 12:28:07 sirius sshd[789]: debug1: Forked child 2159.
Nov 13 12:28:07 sirius sshd[789]: debug3: send_rexec_state: entering fd = 7
config len 1050
Nov 13 12:28:07 sirius sshd[789]: debug3: ssh_msg_send: type 0
Nov 13 12:28:07 sirius sshd[789]: debug3: send_rexec_state: done
Nov 13 12:28:07 sirius sshd[2159]: debug3: oom_adjust_restore
Nov 13 12:28:07 sirius sshd[2159]: debug1: Set /proc/self/oom_score_adj to 0
Nov 13 12:28:07 sirius sshd[2159]: debug1: rexec start in 4 out 4 newsock 4
pipe 6 sock 7
Nov 13 12:28:07 sirius sshd[2159]: debug1: inetd sockets after dupping: 3, 3
Nov 13 12:28:07 sirius sshd[2159]: Connection from 192.168.8.3 port 48708
on 192.168.8.3 port 50400
Nov 13 12:28:07 sirius sshd[2159]: debug1: Client protocol version 2.0;
client software version OpenSSH_7.4p1 Debian-10+deb9u4
Nov 13 12:28:07 sirius sshd[2159]: debug1: match: OpenSSH_7.4p1
Debian-10+deb9u4 pat OpenSSH* compat 0x0400
Nov 13 12:28:07 sirius sshd[2159]: debug1: Local version string
SSH-2.0-OpenSSH_7.4p1 Debian-10+deb9u4
Nov 13 12:28:07 sirius sshd[2159]: debug1: Enabling compatibility mode for
protocol 2.0
Nov 13 12:28:07 sirius sshd[2159]: debug2: fd 3 setting O_NONBLOCK
Nov 13 12:28:07 sirius sshd[2159]: debug3: ssh_sandbox_init: preparing
seccomp filter sandbox
Nov 13 12:28:07 sirius sshd[2159]: debug2: Network child is on pid 2160
Nov 13 12:28:07 sirius sshd[2159]: debug3: preauth child monitor started
Nov 13 12:28:07 sirius sshd[2159]: debug3: privsep user:group 117:65534
[preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug1: permanently_set_uid: 117/65534
[preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug3: ssh_sandbox_child: setting
PR_SET_NO_NEW_PRIVS [preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug3: ssh_sandbox_child: attaching
seccomp filter program [preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug1: list_hostkey_types:
ssh-ed25519,ssh-rsa,rsa-sha2-512,rsa-sha2-256 [preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug3: send packet: type 20 [preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug1: SSH2_MSG_KEXINIT sent [preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug3: receive packet: type 20 [preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug1: SSH2_MSG_KEXINIT received
[preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug2: local server KEXINIT proposal
[preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug2: KEX algorithms:
curve25519-sha...@libssh.org,ecdh-sha2-nistp521,ecdh-sha2-nistp384,ecdh-sha2-nistp256,diffie-hellman-group-exchange-sha256
[preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug2: host key algorithms:
ssh-ed25519,ssh-rsa,rsa-sha2-512,rsa-sha2-256 [preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug2: ciphers ctos:
chacha20-poly1...@openssh.com,aes256-...@openssh.com,aes128-...@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr
[preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug2: ciphers stoc:
chacha20-poly1...@openssh.com,aes256-...@openssh.com,aes128-...@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr
[preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug2: MACs ctos:
hmac-sha2-512-...@openssh.com,hmac-sha2-256-...@openssh.com,
umac-128-...@openssh.com,hmac-sha2-512,hmac-sha2-256,umac-...@openssh.com
[preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug2: MACs stoc:
hmac-sha2-512-...@openssh.com,hmac-sha2-256-...@openssh.com,
umac-128-...@openssh.com,hmac-sha2-512,hmac-sha2-256,umac-...@openssh.com
[preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug2: compression ctos: none [preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug2: compression stoc: none [preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug2: languages ctos:  [preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug2: languages stoc:  [preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug2: first_kex_follows 0  [preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug2: reserved 0  [preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug2: peer client KEXINIT proposal
[preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug2: KEX algorithms:
curve25519-sha...@libssh.org,ecdh-sha2-nistp521,ecdh-sha2-nistp384,ecdh-sha2-nistp256,diffie-hellman-group-exchange-sha256,ext-info-c
[preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug2: host key algorithms:
ssh-ed25519-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com
,ssh-ed25519,ssh-rsa,ecdsa-sha2-nistp521-cert-...@openssh.com,
ecdsa-sha2-nistp384-cert-...@openssh.com,
ecdsa-sha2-nistp256-cert-...@openssh.com,ecdsa-sha2-nistp521,ecdsa-sha2-nistp384,ecdsa-sha2-nistp256
[preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug2: ciphers ctos:
chacha20-poly1...@openssh.com,aes256-...@openssh.com,aes128-...@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr
[preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug2: ciphers stoc:
chacha20-poly1...@openssh.com,aes256-...@openssh.com,aes128-...@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr
[preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug2: MACs ctos:

Re: Mystery interface reported by ip.

[Reco]

Hi.

On Mon, Nov 12, 2018 at 12:54:11PM -0800, pe...@easthope.ca wrote:
> * From: Reco 
> * Date: Fri, 9 Nov 2018 19:56:24 +0300
> > Ok, let's do it the hard way.
> > 
> > udevadm info /sys/class/net/LocLCS218301788
> 
> peter@joule:~$ udevadm info /sys/class/net/LocLCS218301788
> P: /devices/pci:00/:00:1e.0/:02:08.0/net/LocLCS218301788
> E: DEVPATH=/devices/pci:00/:00:1e.0/:02:08.0/net/LocLCS218301788
> E: ID_BUS=pci
> E: ID_MODEL_FROM_DATABASE=82562EZ 10/100 Ethernet Controller
> E: ID_MODEL_ID=0x1050
> E: ID_NET_DRIVER=e100
> E: ID_NET_LINK_FILE=/lib/systemd/network/99-default.link
> E: ID_NET_NAME_MAC=enx0007e978a8b0
> E: ID_NET_NAME_PATH=enp2s8
> E: ID_OUI_FROM_DATABASE=Intel Corporation
> E: ID_PATH=pci-:02:08.0
> E: ID_PATH_TAG=pci-_02_08_0
> E: ID_PCI_CLASS_FROM_DATABASE=Network controller
> E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller
> E: ID_VENDOR_FROM_DATABASE=Intel Corporation
> E: ID_VENDOR_ID=0x8086
> E: IFINDEX=2
> E: INTERFACE=LocLCS218301788
> E: SUBSYSTEM=net
> E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/LocLCS218301788
> E: TAGS=:systemd:
> E: USEC_INITIALIZED=1550444
> 
> > udevadm trigger /sys/class/net/LocLCS218301788
> 
> peter@joule:~$ udevadm trigger /sys/class/net/LocLCS218301788
> [no output]

That's unusual, to say the least. And what about this:

udevadm test /sys/class/net/LocLCS218301788

Reco

video

[aishen]

On est vendredi ? C'est pas aujourd'hui pour les casseroles :)

Re: portable CD players

[Ben Oliver]

On 18-11-10 06:11:34, mick crane wrote:

Does anybody know about these portable CD players like Sony Discman ?
On the PC I
"play stories.m3u"
where "stories.m3u" is just a list of mp3 files from librivox.org

If I put them on a CD will Discman play them, with a menu selection ?
Are they ATRAC or something ?
Any particular format needed ?
Any recommendations for CD player ?

mick


FWIW There are CD players out there that support MP3, if you really have 
to go with CD.


https://www.amazon.co.uk/gp/product/B019J4N5DQ/

You can put MP3s directly onto the disc and play them. This allows you 
to fit a lot more music on.


However, it's less versatile because _every_ CD player you want to use 
with the disc also has to support MP3. Just something to consider.


signature.asc
Description: PGP signature

Re: dans "private joke" il y a "private" et dans "debian-user-french" il y a "french"

[aishen]

Effectivement je m'en étais même pas rendu compte... Tellement sont en 
anglo-saxon


Le 12/11/2018 à 08:06, hamster a écrit :

Et après ca il y a des gens qui ralent parce bernard pose des questions
de newbie…

Le 12/11/2018 à 07:34, aishen a écrit :

Explain ? I don't understand but I guess I am missing something ? lol

Le 11/11/2018 à 20:55, Haricophile a écrit :

Le Sun, 11 Nov 2018 20:23:40 +0100,
aishen  a écrit :


the best and simple skypeforlinux (even if it's microsoft it's very
popular)

even is odd ;)

Re: heads up: timidity causes pulseaudio to not find sound cards

[Eric S Fraga]

On Monday, 12 Nov 2018 at 08:12, deloptes wrote:
> Hi this is known issue, but purging is really not necessary as you could set
> (AFAIK) TIM_ALSASEQ=false
> in /etc/default/timidity

Thanks.

I don't (currently) use timidity so purging was an easy
solution.  However, it's good to know that there is an easier more
elegant solution!

-- 
Eric S Fraga via Emacs 27.0.50 & org 9.1.13 on Debian 9.5

Re: video chat sous Linux/Debian/Sid

[Bernard Schoenacker]

- Mail original -
> De: "aishen" 
> À: debian-user-french@lists.debian.org
> Envoyé: Lundi 12 Novembre 2018 07:34:51
> Objet: Re: video chat sous Linux/Debian/Sid
> 
> Explain ? I don't understand but I guess I am missing something ? lol
> 


England has vote to the brexit, then english spoken is out ...
Schreiben Sie bitte Auf Deutsch ...
Pouvez vous écrire en français ? ...

slt
bernard

Re: Apt geeft rare foutmelding

[Wouter Verhelst]

On Tue, Nov 06, 2018 at 12:00:19PM +0100, Paul van der Vlis wrote:
> Hoi,
> 
> Ik zie dat bug 909000 gerepareerd zou zijn. Nu wou ik proberen Enigmail
> te installeren uit Stretch, maar ik krijg deze melding:
> 
> De volgende pakketten hebben niet-voldane vereisten:
>  enigmail : Vereisten: thunderbird (>= 1:52.0) maar het zal niet
> geïnstalleerd worden of
>icedove (>= 1:52.0)
> E: Kan problemen niet verhelpen, u houdt defecte pakketten vast.
> 
> 
> Ik heb Thunderbird 1:60.2.1-2~deb9u1 geïnstalleerd, dat is toch groter
> of gelijk aan 1:52.0 ?  Wat is dit dan voor een rare melding?

Het probleem is niet de versienummer, het probleem is dat thunderbird
zelf niet geïnstalleerd kan worden. Voor meer details kan je dit doen:

apt -o Debug::pkgProblemResolver=true -o 
Debug::pkgProblemResolver::ShowSources=true install enigmail

Dat geeft een hoop debug messages waaruit je normaal gezien moet kunnen
opmaken waarom het misloopt.

-- 
To the thief who stole my anti-depressants: I hope you're happy

  -- seen somewhere on the Internet on a photo of a billboard

Re: ssh

[Michael Howard]

On 12/11/2018 13:49, Alan Taylor wrote:

Greetings,

I have an ssh problem - one user can use it successfully, another 
cannot. I have checked and rechecked permissions until I am blue in 
the face …
At the moment just trying to ssh into the same machine I am on for the 
problem user (the other user can ssh successfully, both to the console 
machine and outwards to others).
Agent problem ? The successful user was setup in the installation, the 
problem user was added at the command line after initial setup.


Log output follows, appears to fail after the preauth stage …

Any suggestions gratefully accepted

I can't give a definitive answer but I had a similar problem recently. 
The reason I can't be definitive is that it just went away. It was 
though an agent problem and it started following some system upgrades 
and only showed itself on a single box and when being used 
non-interactively.


This doesn't look like your situation but it may be related.

Check for the existence of socket files in /tmp (along the lines of 
/tmp/ssh-/agent.??), on a per user basis. Try to ssh using 
said socket file something along the lines of;


'SSH_AUTH_SOCK=/tmp/ssh-/agent.?? ssh -p blah blah'

this worked for me, but as I say, it weirdly went away before I found 
the real underlying problem. I now don't need to use this mechanism, 
dunno why and I was too busy to continue to track it down.


Hope this helps.

--
Mike Howard

Re: Lire ses logs rapidement de façon efficace

[Belaïd]

Bonjour,

Une solution pas facile facile à mettre en oeuvre mais efficace une fois la
solution mise en place,  le triplet "elasticsearch,  logstach et kibana"

Le dim. 11 nov. 2018 13:58, G2PC  a écrit :

> Bonjour,
>
> Bernard m'avait partagé le paquet ccze pour lire les logs en couleur.
> Ça fonctionne très bien, mais, ça nécessite tout de même de gérer les
> fichiers un après l'autre, ce qui prend du temps.
>
> https://www.visionduweb.eu/wiki/index.php?title=Sommaire_S%C3%A9curit%C3%A9#Des_logs_color.C3.A9s_avec_ccze
>
> N'auriez vous pas une méthode plus facile à utiliser, rapide à mettre en
> oeuvre, simple d'utilisation ?
> ( Voir une intelligence artificielle, capable de faire tout le travail à
> ma place ? )
>
> Merci pour vos avis.
> C'était la question "Linux pour les nuls" du dimanche 11 Novembre 2018.
> ( Le dimanche, tout est permis. )
>
>

Re: Lire ses logs rapidement de façon efficace

[Alexandre Goethals]

J'allais justement évoquer le triplet ElasticSearch.

Par contre c'est très très gourmand en ressources, donc pour une machine 
personnelle, c'est pas la peine: 
https://www.elastic.co/guide/en/elasticsearch/guide/current/hardware.html


Le 12/11/2018 à 13:57, Belaïd a écrit :

Bonjour,

Une solution pas facile facile à mettre en oeuvre mais efficace une 
fois la solution mise en place,  le triplet "elasticsearch,  logstach 
et kibana"


Le dim. 11 nov. 2018 13:58, G2PC > a écrit :


Bonjour,

Bernard m'avait partagé le paquet ccze pour lire les logs en couleur.
Ça fonctionne très bien, mais, ça nécessite tout de même de gérer les
fichiers un après l'autre, ce qui prend du temps.

https://www.visionduweb.eu/wiki/index.php?title=Sommaire_S%C3%A9curit%C3%A9#Des_logs_color.C3.A9s_avec_ccze

N'auriez vous pas une méthode plus facile à utiliser, rapide à
mettre en
oeuvre, simple d'utilisation ?
( Voir une intelligence artificielle, capable de faire tout le
travail à
ma place ? )

Merci pour vos avis.
C'était la question "Linux pour les nuls" du dimanche 11 Novembre
2018.
( Le dimanche, tout est permis. )

Re: buster upgraded postgresql

[mick crane]

On 2018-11-12 13:44, Greg Wooledge wrote:

> > > but how to find out what is this "cluster-name" for pg_ctlcluster,
> > > pg_dropcluster and pg_upgradecluster ?
> >
> > OK from the conf files assume cluster-name is '10/main' and '11/main'
> > respectively ?
>
> default cluster name for both clusters should be "main".
yes I got there eventually


You could also try reading the README.Debian.gz file in
/usr/share/doc/postgresql-*/

In stretch, this is /usr/share/doc/postgresql-9.6/README.Debian.gz
and it contains the exact steps needed to upgrade from 9.1 to 9.4.
Just replace the version numbers with whatever you have.


In my defence I've used msql but have no idea about postgresql and 
thinking there's probably a few things use it I asked.
Looked later but didn't know about "zless" and as it was working didn't 
bother to extract it. I did now so next time I'll be less nervous.


mick

--
Key ID4BFEBB31

Re: Lire ses logs rapidement de façon efficace

[G2PC]

>> 4). Un script maison qui plante…
>> Tout juste ! J'ai pas mal d'utilisateur fantomes qui font toc toc, et, je 
>> veux pouvoir suivre la montée en charge du serveur.
>> Je cherche aussi à analyser mes propres attaques Dos, et, voir ce que 
>> retourne les logs en fonction des outils utilisés pour Dos.
> Tu peux utiliser Ossec (ossec.net) pour analyser des logs, générer des
> alertes et éventuellement des actions sur ces dernières.
>
> Pour le monitoring, j'utilise Icinga2.


Ok, merci, j'avais déjà pu faire une ligne sur Ossec, Icinga2 je n'en
avais pas entendu parler, je rajoute ça à ma petite liste.

Re: Lire ses logs rapidement de façon efficace

[G2PC]

>> Ensuite, je tenterais de stocker les données dans mysql.
> Quel intérêt, franchement ?


Faire compliqué, quand on peut faire simple !

Bernard m'en avait parlé. J'avais aussi pu lire déjà des articles à ce
sujet.
Je crois que ça peut être pratique, lors de sauvegardes, pour conserver
les logs dans une base de données, et, étudier les logs après un plantage.
C'est pour aller plus loin, et, ne pas faire simple ...
Peut être que ce n'est pas tellement nécessaire que ça, mais, j'ai
presque réussi à mettre ça en place, avec rsyslog et Loganalyzer, donc,
autant tester, sur une VM, pour bien être sur que ça puisse fonctionner
normalement.

https://www.visionduweb.eu/wiki/index.php?title=Sommaire_S%C3%A9curit%C3%A9#Adiscon_LogAnalyzer

Re: pushd/popd

[Greg Wooledge]

On Sat, Nov 10, 2018 at 11:58:53PM -0600, David Wright wrote:
> BTW whenever I change directory in scripts, I make sure that I'm in a
> subshell by using ( and ), which guarantees that I get back to the
> same directory however the script finishes.

Depends on the script.  For scripts that change directory more than
once (e.g. a software building script that runs "make" in several
directories, one by one), I concur.  That is sound advice.

For a script that only changes directory once and then does everything
from that directory (e.g. a wrapper), a subshell may be the exact
opposite of what's wanted.  In such cases, you would simply do
"cd /some/where || exit" at the top of the script.

Re: Consulta sobre Raid.

[Matias Mucciolo]

On Monday, November 12, 2018 9:29:29 AM -03 Robert J. Briones C. wrote:
> El vie., 9 nov. 2018 a las 17:07, Matias Mucciolo
> ()
> escribió:
> > On Friday, November 9, 2018 5:01:25 PM -03 Robert J. Briones C. wrote:
> > > El vie., 9 nov. 2018 a las 16:50, Matias Mucciolo
> > > ()
> > > 
> > > escribió:
> > > > On Friday, November 9, 2018 4:47:48 PM -03 Robert J. Briones C. wrote:
> > > > > El vie., 9 nov. 2018 a las 16:45, Matias Mucciolo
> > > > > ()
> > > > > 
> > > > > escribió:
> > > > > > On Friday, November 9, 2018 4:40:46 PM -03 Robert J. Briones C.
> > 
> > wrote:
> > > > > > > El vie., 9 nov. 2018 a las 16:24, Matias Mucciolo
> > > > > > > ()
> > > > > > > 
> > > > > > > escribió:
> > > > > > > > On Friday, November 9, 2018 12:41:04 PM -03 Robert J. Briones
> > 
> > C.
> > 
> > > > wrote:
> > > > > > > > > Estimados.
> > > > > > > > > 
> > > > > > > > > Buenos dias,
> > > > > > > > > 
> > > > > > > > > tengo un pequeño servidor montado de manera normal (novato).
> > > > > > > > > 
> > > > > > > > > y necesito sacar información de otro disco duro que he
> > > > > > > > > conectado,
> > > > > > 
> > > > > > pero
> > > > > > 
> > > > > > > > > parece que esta en RAID y de Raid no se prácticamente nada.
> > > > > > > > > 
> > > > > > > > > fdisk .l :
> > > > > > > > > 
> > > > > > > > > Device   StartEndSectors  Size Type
> > > > > > > > > /dev/sdb1 2048   4095   20481M BIOS boot
> > > > > > > > > /dev/sdb2 409610485751044480  510M Linux RAID
> > > > > > > > > /dev/sdb3  1048576 1953523711 1952475136  931G Linux RAID
> > > > > > > > > la que quiero montar es la /dev/sdb3
> > > > > > > > > 
> > > > > > > > > solo quiero sacar unos datos de ahí, es posible de manera
> > 
> > fácil,
> > 
> > > > sin
> > > > 
> > > > > > > > tener
> > > > > > > > 
> > > > > > > > > que montar un raid completo o algo así ?
> > > > > > > > > 
> > > > > > > > > se los agradecería.
> > > > > > > > > 
> > > > > > > > > Saludos.
> > > > > > > > 
> > > > > > > > Buenas
> > > > > > > > no te detecta el raid ya ?
> > > > > > > > pasate la salida del comando:
> > > > > > > > 
> > > > > > > > cat /proc/mdstat
> > > > > > > > 
> > > > > > > > si no existe el archivo o esta vacio ejemplo:
> > > > > > > > cat /proc/mdstat
> > > > > > > > Personalities :
> > > > > > > > unused devices: 
> > > > > > > > 
> > > > > > > > sabes que raid tenia ? suponiendo que es RAID1
> > > > > > > > carga el modulo raid1 ejemplo
> > > > > > > > modprobe raid1
> > > > > > > > y volve a mirar el archivo anterior.
> > > > > > > > 
> > > > > > > > 
> > > > > > > > saludos
> > > > > > > > Matias
> > > > > > > 
> > > > > > > cat /proc/mdstat
> > > > > > > Personalities : [raid1]
> > > > > > > md1 : active (auto-read-only) raid1 sdb3[5]
> > > > > > > 
> > > > > > >   976106304 blocks super 1.2 [3/1] [__U]
> > > > > > > 
> > > > > > > md0 : active (auto-read-only) raid1 sdb2[5]
> > > > > > > 
> > > > > > >   521920 blocks super 1.2 [3/1] [__U]
> > > > > > > 
> > > > > > > eso quiere decir que esta montado ? como debería acceder a sus
> > 
> > datos
> > 
> > > > ?
> > > > 
> > > > > > > Saludos.
> > > > > > 
> > > > > > (acordate de contestar a la lista principalmente.)
> > > > > > 
> > > > > > eso es bueno...ahora podes montarla usando el device de raid
> > > > > > en este caso es /dev/md1 para la particion sdb3
> > > > > > 
> > > > > > ejemplo
> > > > > > 
> > > > > > mount /dev/md1 /mnt
> > > > > > 
> > > > > > deberia montarlo en el dir /mnt.. si ves que no lo monta mira el
> > 
> > dmesg
> > 
> > > > > > y los logs buscando errores.
> > > > > > 
> > > > > > saludos
> > > > > > Matias.-
> > > > > 
> > > > > mount /dev/md1 /mnt/raid
> > > > > mount: unknown filesystem type 'LVM2_member'
> > > > > 
> > > > > intento montar y me aparece eso .
> > > > 
> > > > oh jajaja ahora vas a tener que pelear con lvm
> > > > 
> > > > pasate la salida de los comandos
> > > > pvdisplay y lvdisplay
> > > > 
> > > > Matias
> > > 
> > > jajaja, siempre a mi !!., jaja
> > > 
> > > ejecute lo que me dijiste pero me dice
> > > 
> > > bash: pvdisplay: no se encontró la orden
> > > bash: lvdisplay: no se encontró la orden
> > > 
> > > y en los paquetes no esta tampoco .-
> > > 
> > > estoy haciendo algo mal ?
> > > 
> > > saludos.
> > 
> > esos comandos vienen en el paquete lvm2
> > trata de instalar ese paquete y despues
> > si es posible renicia la maquina
> > asi te levanta automaticamente los lvm
> > y despues is ejecuta los comandos esos.
> > 
> > si no podes reniciar la maquina
> > vas a tener que levantar el lvm a mano
> > que ahora no recuerdo pero supongo que seria
> > con vgscan o algo asi
> 
> Buenos dias a todos.
> 
> retomando este tema, instale Lvm2 y ejecute los comandos... este es el
> resultado.
> 
> 
> pvdisplay
>   --- Physical volume ---
>   PV Name   /dev/md1
>   VG Name   pve
>   PV Size   930,89 GiB / not usable 4,81 MiB
>   Allocatable   yes
>   PE Size

Re: portable CD players

[Greg Wooledge]

On Sat, Nov 10, 2018 at 10:47:11AM -0500, rhkra...@gmail.com wrote:
> IIRC, a CD holds a maximum of 80 minutes .wav sound.  (Around 800MB, about 1 
> MB per minute).  A 4 GB holds way more than that in .mp3, although a figure 
> doesn't come to mind at the moment -- maybe more on the order of 40 hours of 
> sound.  And, it is reprogrammable.

For starters, your "1 MB per minute" math is off.  Even using the numbers
you showed, that's 10 MB per minute.

128 kbps MP3 (a de facto standard encoding bit rate from many years ago)
is an 8:1 compression over regular CD-quality audio.  This one is about
"a meg a minute".  At least as a first-order approximation.

So, a gigabyte of 128 kbps MP3 audio data is about a thousand megs,
therefore about a thousand minutes, or 17 hours.  At 4 GB, you're looking
at about 67 hours.

Of course, not all audio data is compressed at a bit rate of 128 kbps.
In more recent years, with storage and bandwith prices dropping, people
have started using much higher bit rates on music files.  It's not
at all uncommon to see MP3 encoded at 256 kbps or higher these days.
That drops you to 33 hours for a 4 GB storage device.

If your music library contains a mixture of songs encoded at varying
bit rates, you'll probably be somewhere in between these values.

And not all audio data is music.  Human speech can be compressed at a
much lower bit rate than music.  A quick google search tells me that
64 kbps is common for audio books.  That bumps you up to 133 hours, if
you're storing MP3 audio books.  Possibly more, since 64 kbps seems to be
an upper bound on speech encoding.

There are also dedicated speech encoding algorithms.  Speex was one of
them, but I believe it never really caught on.  I think it was obsoleted
by the Opus codec, which is starting to catch on a little bit.

According to 
the recommended Opus bitrate for audio books is 24 kbps for mono, or
32 kbps for stereo.

The problem with Opus is that a hardware player may not support it.
The most recent hardware player that I've got (several years old) does
not support Opus, but it does support Ogg Vorbis, MP3, WMA and other
formats that have been around for decades.

Re: Consulta sobre Raid.

[Matias Mucciolo]

On Saturday, November 10, 2018 4:30:30 PM -03 Galvatorix Torixgalva wrote:
> Hola,
> 
> Creo, y digo creo, que o consigues todos los discos del raid. o te
> olvidas.
> 
> Raid tiene cosas positivas y cosas negativas. Las positivas son muy
> positivas y las negativas son muy negativas.
> 
> Podrías consultar con empresas especializadas si es posible, pero algo así
> no creo que sea barato.
> 
> Saludos

Por favor no des-informes a la gente..(y lee todo el hilo en lo posible)
un raid 1 se puede montar sin problemas con solo
tener un disco.

Robert pudiste montar ver lvm ?

saludos.
Matias.

Re: ssh

[Alan Taylor]

No, both users have rsa and ed25519 keys only.
On 12 Nov 2018, 22:07 +0800, Freek de Kruijf , wrote:
> Op maandag 12 november 2018 14:49:23 CET schreef Alan Taylor:
> > Greetings,
> >
> > I have an ssh problem - one user can use it successfully, another cannot. I
> > have checked and rechecked permissions until I am blue in the face … At the
> > moment just trying to ssh into the same machine I am on for the problem
> > user (the other user can ssh successfully, both to the console machine and
> > outwards to others). Agent problem ? The successful user was setup in the
> > installation, the problem user was added at the command line after initial
> > setup.
> >
> > Log output follows, appears to fail after the preauth stage …
> >
> > Any suggestions gratefully accepted
> >
> > root@sirius/etc/ssh # journalctl | grep sshd | grep "Nov 12 13:45"
> > Nov 12 13:45:17 sirius sshd[3155]: debug3: fd 4 is not O_NONBLOCK
> > Nov 12 13:45:17 sirius sshd[3155]: debug1: Forked child 3241.
> > Nov 12 13:45:17 sirius sshd[3155]: debug3: send_rexec_state: entering fd = 7
> > config len 650 Nov 12 13:45:17 sirius sshd[3155]: debug3: ssh_msg_send:
> > type 0
> > Nov 12 13:45:17 sirius sshd[3241]: debug3: oom_adjust_restore
> > Nov 12 13:45:17 sirius sshd[3155]: debug3: send_rexec_state: done
> > Nov 12 13:45:17 sirius sshd[3241]: debug1: Set /proc/self/oom_score_adj to 0
> > Nov 12 13:45:17 sirius sshd[3241]: debug1: rexec start in 4 out 4 newsock 4
> > pipe 6 sock 7 Nov 12 13:45:17 sirius sshd[3241]: debug1: inetd sockets
> > after dupping: 3, 3 Nov 12 13:45:17 sirius sshd[3241]: Connection from
> > 192.168.8.3 port 39668 on 192.168.8.3 port 50400 Nov 12 13:45:17 sirius
> > sshd[3241]: debug1: Client protocol version 2.0; client software version
> > OpenSSH_7.4p1 Debian-10+deb9u4 Nov 12 13:45:17 sirius sshd[3241]: debug1:
> > match: OpenSSH_7.4p1 Debian-10+deb9u4 pat OpenSSH* compat 0x0400 Nov 12
> > 13:45:17 sirius sshd[3241]: debug1: Local version string
> > SSH-2.0-OpenSSH_7.4p1 Debian-10+deb9u4 Nov 12 13:45:17 sirius sshd[3241]:
> > debug1: Enabling compatibility mode for protocol 2.0 Nov 12 13:45:17 sirius
> > sshd[3241]: debug2: fd 3 setting O_NONBLOCK Nov 12 13:45:17 sirius
> > sshd[3241]: debug3: ssh_sandbox_init: preparing seccomp filter sandbox Nov
> > 12 13:45:17 sirius sshd[3241]: debug2: Network child is on pid 3242 Nov 12
> > 13:45:17 sirius sshd[3241]: debug3: preauth child monitor started Nov 12
> > 13:45:17 sirius sshd[3241]: debug3: privsep user:group 117:65534 [preauth]
> > Nov 12 13:45:17 sirius sshd[3241]: debug1: permanently_set_uid: 117/65534
> > [preauth] Nov 12 13:45:17 sirius sshd[3241]: debug3: ssh_sandbox_child:
> > setting PR_SET_NO_NEW_PRIVS [preauth] Nov 12 13:45:17 sirius sshd[3241]:
> > debug3: ssh_sandbox_child: attaching seccomp filter program [preauth] Nov
> > 12 13:45:17 sirius sshd[3241]: debug1: list_hostkey_types:
> > ssh-ed25519,ssh-rsa,rsa-sha2-512,rsa-sha2-256 [preauth] Nov 12 13:45:17
> > sirius sshd[3241]: debug3: send packet: type 20 [preauth] Nov 12 13:45:17
> > sirius sshd[3241]: debug1: SSH2_MSG_KEXINIT sent [preauth] Nov 12 13:45:17
> > sirius sshd[3241]: debug3: receive packet: type 20 [preauth] Nov 12
> > 13:45:17 sirius sshd[3241]: debug1: SSH2_MSG_KEXINIT received [preauth] Nov
> > 12 13:45:17 sirius sshd[3241]: debug2: local server KEXINIT proposal
> > [preauth] Nov 12 13:45:17 sirius sshd[3241]: debug2: KEX algorithms:
> > curve25519-sha256,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2
> > -nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hel
> > lman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha
> > 256,diffie-hellman-group14-sha1 [preauth] Nov 12 13:45:17 sirius sshd[3241]:
> > debug2: host key algorithms: ssh-ed25519,ssh-rsa,rsa-sha2-512,rsa-sha2-256
> > [preauth] Nov 12 13:45:17 sirius sshd[3241]: debug2: ciphers ctos:
> > chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@o
> > penssh.com,aes256-...@openssh.com[preauth] Nov 12 13:45:17 sirius
> > sshd[3241]: debug2: ciphers stoc:
> > chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@o
> > penssh.com,aes256-...@openssh.com[preauth] Nov 12 13:45:17 sirius
> > sshd[3241]: debug2: MACs ctos:
> > umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-etm@openssh.
> > com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac-64@openssh.
> > com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 [preauth] Nov
> > 12 13:45:17 sirius sshd[3241]: debug2: MACs stoc:
> > umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-etm@openssh.
> > com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac-64@openssh.
> > com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 [preauth] Nov
> > 12 13:45:17 sirius sshd[3241]: debug2: compression ctos: none [preauth] Nov
> > 12 13:45:17 sirius sshd[3241]: debug2: compression stoc: none [preauth] Nov
> > 12 13:45:17 sirius 

Re: Consulta sobre Raid.

[Robert J. Briones C.]

El vie., 9 nov. 2018 a las 17:07, Matias Mucciolo ()
escribió:

>
> On Friday, November 9, 2018 5:01:25 PM -03 Robert J. Briones C. wrote:
> > El vie., 9 nov. 2018 a las 16:50, Matias Mucciolo
> > ()
> > escribió:
> > > On Friday, November 9, 2018 4:47:48 PM -03 Robert J. Briones C. wrote:
> > > > El vie., 9 nov. 2018 a las 16:45, Matias Mucciolo
> > > > ()
> > > >
> > > > escribió:
> > > > > On Friday, November 9, 2018 4:40:46 PM -03 Robert J. Briones C.
> wrote:
> > > > > > El vie., 9 nov. 2018 a las 16:24, Matias Mucciolo
> > > > > > ()
> > > > > >
> > > > > > escribió:
> > > > > > > On Friday, November 9, 2018 12:41:04 PM -03 Robert J. Briones
> C.
> > >
> > > wrote:
> > > > > > > > Estimados.
> > > > > > > >
> > > > > > > > Buenos dias,
> > > > > > > >
> > > > > > > > tengo un pequeño servidor montado de manera normal (novato).
> > > > > > > >
> > > > > > > > y necesito sacar información de otro disco duro que he
> > > > > > > > conectado,
> > > > >
> > > > > pero
> > > > >
> > > > > > > > parece que esta en RAID y de Raid no se prácticamente nada.
> > > > > > > >
> > > > > > > > fdisk .l :
> > > > > > > >
> > > > > > > > Device   StartEndSectors  Size Type
> > > > > > > > /dev/sdb1 2048   4095   20481M BIOS boot
> > > > > > > > /dev/sdb2 409610485751044480  510M Linux RAID
> > > > > > > > /dev/sdb3  1048576 1953523711 1952475136  931G Linux RAID
> > > > > > > > la que quiero montar es la /dev/sdb3
> > > > > > > >
> > > > > > > > solo quiero sacar unos datos de ahí, es posible de manera
> fácil,
> > >
> > > sin
> > >
> > > > > > > tener
> > > > > > >
> > > > > > > > que montar un raid completo o algo así ?
> > > > > > > >
> > > > > > > > se los agradecería.
> > > > > > > >
> > > > > > > > Saludos.
> > > > > > >
> > > > > > > Buenas
> > > > > > > no te detecta el raid ya ?
> > > > > > > pasate la salida del comando:
> > > > > > >
> > > > > > > cat /proc/mdstat
> > > > > > >
> > > > > > > si no existe el archivo o esta vacio ejemplo:
> > > > > > > cat /proc/mdstat
> > > > > > > Personalities :
> > > > > > > unused devices: 
> > > > > > >
> > > > > > > sabes que raid tenia ? suponiendo que es RAID1
> > > > > > > carga el modulo raid1 ejemplo
> > > > > > > modprobe raid1
> > > > > > > y volve a mirar el archivo anterior.
> > > > > > >
> > > > > > >
> > > > > > > saludos
> > > > > > > Matias
> > > > > >
> > > > > > cat /proc/mdstat
> > > > > > Personalities : [raid1]
> > > > > > md1 : active (auto-read-only) raid1 sdb3[5]
> > > > > >
> > > > > >   976106304 blocks super 1.2 [3/1] [__U]
> > > > > >
> > > > > > md0 : active (auto-read-only) raid1 sdb2[5]
> > > > > >
> > > > > >   521920 blocks super 1.2 [3/1] [__U]
> > > > > >
> > > > > > eso quiere decir que esta montado ? como debería acceder a sus
> datos
> > >
> > > ?
> > >
> > > > > > Saludos.
> > > > >
> > > > > (acordate de contestar a la lista principalmente.)
> > > > >
> > > > > eso es bueno...ahora podes montarla usando el device de raid
> > > > > en este caso es /dev/md1 para la particion sdb3
> > > > >
> > > > > ejemplo
> > > > >
> > > > > mount /dev/md1 /mnt
> > > > >
> > > > > deberia montarlo en el dir /mnt.. si ves que no lo monta mira el
> dmesg
> > > > > y los logs buscando errores.
> > > > >
> > > > > saludos
> > > > > Matias.-
> > > >
> > > > mount /dev/md1 /mnt/raid
> > > > mount: unknown filesystem type 'LVM2_member'
> > > >
> > > > intento montar y me aparece eso .
> > >
> > > oh jajaja ahora vas a tener que pelear con lvm
> > >
> > > pasate la salida de los comandos
> > > pvdisplay y lvdisplay
> > >
> > > Matias
> >
> > jajaja, siempre a mi !!., jaja
> >
> > ejecute lo que me dijiste pero me dice
> >
> > bash: pvdisplay: no se encontró la orden
> > bash: lvdisplay: no se encontró la orden
> >
> > y en los paquetes no esta tampoco .-
> >
> > estoy haciendo algo mal ?
> >
> > saludos.
>
> esos comandos vienen en el paquete lvm2
> trata de instalar ese paquete y despues
> si es posible renicia la maquina
> asi te levanta automaticamente los lvm
> y despues is ejecuta los comandos esos.
>
> si no podes reniciar la maquina
> vas a tener que levantar el lvm a mano
> que ahora no recuerdo pero supongo que seria
> con vgscan o algo asi


Buenos dias a todos.

retomando este tema, instale Lvm2 y ejecute los comandos... este es el
resultado.


pvdisplay
  --- Physical volume ---
  PV Name   /dev/md1
  VG Name   pve
  PV Size   930,89 GiB / not usable 4,81 MiB
  Allocatable   yes
  PE Size   4,00 MiB
  Total PE  238306
  Free PE   4062
  Allocated PE  234244
  PV UUID   OAwnHT-rz8q-goQK-nb6X-xu4I-24r6-8jfMjq


 lvdisplay
  --- Logical volume ---
  LV Path/dev/pve/swap
  LV Nameswap
  VG Namepve
  LV UUIDifrkAs-AIlb-ok29-xGPH-A9ij-T9T5-pxW7kr
  LV Write Accessread/write
  LV Creation host, time proxmox, 2014-08-19 05:53:15 

Re: Lire ses logs rapidement de façon efficace

[Ph. Gras]

Salut,

> 4). Un script maison qui plante…
> Tout juste ! J'ai pas mal d'utilisateur fantomes qui font toc toc, et, je 
> veux pouvoir suivre la montée en charge du serveur.
> Je cherche aussi à analyser mes propres attaques Dos, et, voir ce que 
> retourne les logs en fonction des outils utilisés pour Dos.

Fail2ban est un logiciel que tu devrais connaître, dont le rôle est de passer à 
iptables les IP de tout un tas d'emmerdeurs…

Il analyse les logs selon des expressions régulières correspondant à des 
(filtres) scénarii d'attaques, que tu peux enrichir.
Lorsqu'une IP est détectée selon tel filtre, il l'intègre dans une règle 
iptables qui les bannit.

Ça diminue vachement le trafic parasite, et du coup tu es nettement plus serein 
question charge du serveur.

> Je cherche en parallèle a finir mon tutoriel sur mod_evasive, en testant 
> cette mod.

Ce qui rendrait par conséquent le module évasive d'Apache quelque peu superflu…

Il existe d'autres outils du même genre, mais dont je ne me souviens plus des 
noms.

> Ensuite, j'ai le redmine qui tourne depuis quelques semaines, je voudrais 
> suivre les éventuels problèmes liés à ruby.
> J'ai aussi les Vhosts à améliorer un peu il me semble, donc, si d'éventuelles 
> erreurs s'ajoutent au log, j'aimerais pouvoir les consulter sans devoir 
> toujours aller sur le terminal.
> 
> Pour cela, comme déjà évoqué dans ma précédente réponse, j'ai installé 
> Loganalyzer.
> J'ai préféré commencer par une lecture directe du fichier syslog, je dois 
> attendre une première rotation de log pour voir si loganalyzer va bien avoir 
> les droits de lire syslog.

Pour ce faire, Logwatch me semble tout à fait adéquat. Il t'envoie tous les 
matins un rapport de tout ce qui a déconné lors
de la journée précédente, ce qui t'évite de perdre un temps fou sur le 
terminal, tu y vas juste pour vérifier, comprendre, et
enfin réparer d'éventuelles erreurs de configuration, ou prendre les mesures 
qui s'imposent dans tel cas précis.

> Ensuite, je tenterais de stocker les données dans mysql.

Quel intérêt, franchement ?

Bonne journée,

Ph. Gras

Re: Consulta sobre Raid.

[Robert J. Briones C.]

El lun., 12 nov. 2018 a las 9:12, Matias Mucciolo ()
escribió:

>
> On Saturday, November 10, 2018 4:30:30 PM -03 Galvatorix Torixgalva wrote:
> > Hola,
> >
> > Creo, y digo creo, que o consigues todos los discos del raid. o te
> > olvidas.
> >
> > Raid tiene cosas positivas y cosas negativas. Las positivas son muy
> > positivas y las negativas son muy negativas.
> >
> > Podrías consultar con empresas especializadas si es posible, pero algo
> así
> > no creo que sea barato.
> >
> > Saludos
>
> Por favor no des-informes a la gente..(y lee todo el hilo en lo posible)
> un raid 1 se puede montar sin problemas con solo
> tener un disco.
>
> Robert pudiste montar ver lvm ?
>
> saludos.
> Matias.
>

Hola Matías,.

Acabo de retomar y responder en el hilo original.

Gracias.

Saludos.

Re: Consulta sobre Raid.

[Robert J. Briones C.]

El lun., 12 nov. 2018 a las 9:45, Matias Mucciolo ()
escribió:

>
> On Monday, November 12, 2018 9:29:29 AM -03 Robert J. Briones C. wrote:
> > El vie., 9 nov. 2018 a las 17:07, Matias Mucciolo
> > ()
> > escribió:
> > > On Friday, November 9, 2018 5:01:25 PM -03 Robert J. Briones C. wrote:
> > > > El vie., 9 nov. 2018 a las 16:50, Matias Mucciolo
> > > > ()
> > > >
> > > > escribió:
> > > > > On Friday, November 9, 2018 4:47:48 PM -03 Robert J. Briones C.
> wrote:
> > > > > > El vie., 9 nov. 2018 a las 16:45, Matias Mucciolo
> > > > > > ()
> > > > > >
> > > > > > escribió:
> > > > > > > On Friday, November 9, 2018 4:40:46 PM -03 Robert J. Briones C.
> > >
> > > wrote:
> > > > > > > > El vie., 9 nov. 2018 a las 16:24, Matias Mucciolo
> > > > > > > > ()
> > > > > > > >
> > > > > > > > escribió:
> > > > > > > > > On Friday, November 9, 2018 12:41:04 PM -03 Robert J.
> Briones
> > >
> > > C.
> > >
> > > > > wrote:
> > > > > > > > > > Estimados.
> > > > > > > > > >
> > > > > > > > > > Buenos dias,
> > > > > > > > > >
> > > > > > > > > > tengo un pequeño servidor montado de manera normal
> (novato).
> > > > > > > > > >
> > > > > > > > > > y necesito sacar información de otro disco duro que he
> > > > > > > > > > conectado,
> > > > > > >
> > > > > > > pero
> > > > > > >
> > > > > > > > > > parece que esta en RAID y de Raid no se prácticamente
> nada.
> > > > > > > > > >
> > > > > > > > > > fdisk .l :
> > > > > > > > > >
> > > > > > > > > > Device   StartEndSectors  Size Type
> > > > > > > > > > /dev/sdb1 2048   4095   20481M BIOS boot
> > > > > > > > > > /dev/sdb2 409610485751044480  510M Linux RAID
> > > > > > > > > > /dev/sdb3  1048576 1953523711 1952475136  931G Linux RAID
> > > > > > > > > > la que quiero montar es la /dev/sdb3
> > > > > > > > > >
> > > > > > > > > > solo quiero sacar unos datos de ahí, es posible de manera
> > >
> > > fácil,
> > >
> > > > > sin
> > > > >
> > > > > > > > > tener
> > > > > > > > >
> > > > > > > > > > que montar un raid completo o algo así ?
> > > > > > > > > >
> > > > > > > > > > se los agradecería.
> > > > > > > > > >
> > > > > > > > > > Saludos.
> > > > > > > > >
> > > > > > > > > Buenas
> > > > > > > > > no te detecta el raid ya ?
> > > > > > > > > pasate la salida del comando:
> > > > > > > > >
> > > > > > > > > cat /proc/mdstat
> > > > > > > > >
> > > > > > > > > si no existe el archivo o esta vacio ejemplo:
> > > > > > > > > cat /proc/mdstat
> > > > > > > > > Personalities :
> > > > > > > > > unused devices: 
> > > > > > > > >
> > > > > > > > > sabes que raid tenia ? suponiendo que es RAID1
> > > > > > > > > carga el modulo raid1 ejemplo
> > > > > > > > > modprobe raid1
> > > > > > > > > y volve a mirar el archivo anterior.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > saludos
> > > > > > > > > Matias
> > > > > > > >
> > > > > > > > cat /proc/mdstat
> > > > > > > > Personalities : [raid1]
> > > > > > > > md1 : active (auto-read-only) raid1 sdb3[5]
> > > > > > > >
> > > > > > > >   976106304 blocks super 1.2 [3/1] [__U]
> > > > > > > >
> > > > > > > > md0 : active (auto-read-only) raid1 sdb2[5]
> > > > > > > >
> > > > > > > >   521920 blocks super 1.2 [3/1] [__U]
> > > > > > > >
> > > > > > > > eso quiere decir que esta montado ? como debería acceder a
> sus
> > >
> > > datos
> > >
> > > > > ?
> > > > >
> > > > > > > > Saludos.
> > > > > > >
> > > > > > > (acordate de contestar a la lista principalmente.)
> > > > > > >
> > > > > > > eso es bueno...ahora podes montarla usando el device de raid
> > > > > > > en este caso es /dev/md1 para la particion sdb3
> > > > > > >
> > > > > > > ejemplo
> > > > > > >
> > > > > > > mount /dev/md1 /mnt
> > > > > > >
> > > > > > > deberia montarlo en el dir /mnt.. si ves que no lo monta mira
> el
> > >
> > > dmesg
> > >
> > > > > > > y los logs buscando errores.
> > > > > > >
> > > > > > > saludos
> > > > > > > Matias.-
> > > > > >
> > > > > > mount /dev/md1 /mnt/raid
> > > > > > mount: unknown filesystem type 'LVM2_member'
> > > > > >
> > > > > > intento montar y me aparece eso .
> > > > >
> > > > > oh jajaja ahora vas a tener que pelear con lvm
> > > > >
> > > > > pasate la salida de los comandos
> > > > > pvdisplay y lvdisplay
> > > > >
> > > > > Matias
> > > >
> > > > jajaja, siempre a mi !!., jaja
> > > >
> > > > ejecute lo que me dijiste pero me dice
> > > >
> > > > bash: pvdisplay: no se encontró la orden
> > > > bash: lvdisplay: no se encontró la orden
> > > >
> > > > y en los paquetes no esta tampoco .-
> > > >
> > > > estoy haciendo algo mal ?
> > > >
> > > > saludos.
> > >
> > > esos comandos vienen en el paquete lvm2
> > > trata de instalar ese paquete y despues
> > > si es posible renicia la maquina
> > > asi te levanta automaticamente los lvm
> > > y despues is ejecuta los comandos esos.
> > >
> > > si no podes reniciar la maquina
> > > vas a tener que levantar el lvm a mano
> > > que ahora no recuerdo pero supongo que seria
> > > con vgscan o algo asi
> >
> > 

Re: buster upgraded postgresql

[Greg Wooledge]

> > > > but how to find out what is this "cluster-name" for pg_ctlcluster,
> > > > pg_dropcluster and pg_upgradecluster ?
> > > 
> > > OK from the conf files assume cluster-name is '10/main' and '11/main'
> > > respectively ?
> > 
> > default cluster name for both clusters should be "main".
> yes I got there eventually

You could also try reading the README.Debian.gz file in
/usr/share/doc/postgresql-*/

In stretch, this is /usr/share/doc/postgresql-9.6/README.Debian.gz
and it contains the exact steps needed to upgrade from 9.1 to 9.4.
Just replace the version numbers with whatever you have.

ssh

[Alan Taylor]

Greetings,

I have an ssh problem - one user can use it successfully, another cannot. I 
have checked and rechecked permissions until I am blue in the face …
At the moment just trying to ssh into the same machine I am on for the problem 
user (the other user can ssh successfully, both to the console machine and 
outwards to others).
Agent problem ? The successful user was setup in the installation, the problem 
user was added at the command line after initial setup.

Log output follows, appears to fail after the preauth stage …

Any suggestions gratefully accepted

root@sirius/etc/ssh # journalctl | grep sshd | grep "Nov 12 13:45"
Nov 12 13:45:17 sirius sshd[3155]: debug3: fd 4 is not O_NONBLOCK
Nov 12 13:45:17 sirius sshd[3155]: debug1: Forked child 3241.
Nov 12 13:45:17 sirius sshd[3155]: debug3: send_rexec_state: entering fd = 7 
config len 650
Nov 12 13:45:17 sirius sshd[3155]: debug3: ssh_msg_send: type 0
Nov 12 13:45:17 sirius sshd[3241]: debug3: oom_adjust_restore
Nov 12 13:45:17 sirius sshd[3155]: debug3: send_rexec_state: done
Nov 12 13:45:17 sirius sshd[3241]: debug1: Set /proc/self/oom_score_adj to 0
Nov 12 13:45:17 sirius sshd[3241]: debug1: rexec start in 4 out 4 newsock 4 
pipe 6 sock 7
Nov 12 13:45:17 sirius sshd[3241]: debug1: inetd sockets after dupping: 3, 3
Nov 12 13:45:17 sirius sshd[3241]: Connection from 192.168.8.3 port 39668 on 
192.168.8.3 port 50400
Nov 12 13:45:17 sirius sshd[3241]: debug1: Client protocol version 2.0; client 
software version OpenSSH_7.4p1 Debian-10+deb9u4
Nov 12 13:45:17 sirius sshd[3241]: debug1: match: OpenSSH_7.4p1 
Debian-10+deb9u4 pat OpenSSH* compat 0x0400
Nov 12 13:45:17 sirius sshd[3241]: debug1: Local version string 
SSH-2.0-OpenSSH_7.4p1 Debian-10+deb9u4
Nov 12 13:45:17 sirius sshd[3241]: debug1: Enabling compatibility mode for 
protocol 2.0
Nov 12 13:45:17 sirius sshd[3241]: debug2: fd 3 setting O_NONBLOCK
Nov 12 13:45:17 sirius sshd[3241]: debug3: ssh_sandbox_init: preparing seccomp 
filter sandbox
Nov 12 13:45:17 sirius sshd[3241]: debug2: Network child is on pid 3242
Nov 12 13:45:17 sirius sshd[3241]: debug3: preauth child monitor started
Nov 12 13:45:17 sirius sshd[3241]: debug3: privsep user:group 117:65534 
[preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug1: permanently_set_uid: 117/65534 
[preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug3: ssh_sandbox_child: setting 
PR_SET_NO_NEW_PRIVS [preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug3: ssh_sandbox_child: attaching seccomp 
filter program [preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug1: list_hostkey_types: 
ssh-ed25519,ssh-rsa,rsa-sha2-512,rsa-sha2-256 [preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug3: send packet: type 20 [preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug1: SSH2_MSG_KEXINIT sent [preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug3: receive packet: type 20 [preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug1: SSH2_MSG_KEXINIT received [preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug2: local server KEXINIT proposal 
[preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug2: KEX algorithms: 
curve25519-sha256,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1
 [preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug2: host key algorithms: 
ssh-ed25519,ssh-rsa,rsa-sha2-512,rsa-sha2-256 [preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug2: ciphers ctos: 
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com[preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug2: ciphers stoc: 
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com[preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug2: MACs ctos: 
umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
 [preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug2: MACs stoc: 
umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
 [preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug2: compression ctos: none [preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug2: compression stoc: none [preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug2: languages ctos: [preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug2: languages stoc: [preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug2: first_kex_follows 0 [preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug2: reserved 0 [preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug2: peer client KEXINIT proposal 
[preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug2: KEX algorithms: 

Re: Filosofía: RAID vs particiones en sistema hogareño [TERMINADO]

[Javier ArgentinaBBAR]

El mar., 23 oct. 2018 a las 14:13, Javier ArgentinaBBAR
() escribió:
>
> Buenas tardes:
>
> La siguiente es una pregunta para debate y escuchar opiniones, no para
> corregir problemas.
>
> Desde hace 14 años uso GNU/Linux, y siempre he usado particiones.
> Con el tiempo, el crecimiento de datos y baja de precios relativos de
> discos, ha hecho que usara más de un disco en mi sistema personal.
> Los he manejado hasta ahora como discos independientes, y me las he
> arreglado para que sea transparente a los usuarios, o sea, mi familia.
>
> Pero he estado pensando si no convendría pasar a armar un RAID con
> mdadm, y "olvidarme" del manejo de cuotas de disco (una de las cosas
> que hago para poner coto a la expansión de datos).
> No me cabe dudas que en un sistema de producción debo usar RAID, pero
> en mi casa...  aún no encuentro argumentos suficientes como para
> hacerlo.
>
> Por eso la pregunta es:
> En un sistema hogareño, ¿usarían RAID?
> Como aclaración, el sistema tiene dos discos con "datos de uso" y un
> tercero con "copia de seguridad de datos sensibles", que, por
> supuesto, este último no entraría en el RAID a armar con los otros
> dos.
>
> Muchas gracias a todos
>
> JAP

Visto que mi objetivo era aumentar el lugar disponible en disco y
además tomar las medidas necesarias para preservar la integridad de la
información, es que me decidí por montar un RAID-5 en el sistema de mi
casa, con 3 discos de 1 TB cada uno.
De esa manera, pasaría de la configuración de un disco de 1 TB, a un
RAID de 2 TB, asegurando los datos.
Practiqué unas 5 o 6 veces con máquina virtual, hasta que el fin de
semana lo hice con los discos físicos.

Conclusión: RAID es una porquería.
Tardé 4 horas, 20 minutos en instalar un sistema Debian básico. Cuando
digo básico, me refiero a básico en absoluto, sin entorno gráfico, sin
servidor de impresión, y sin "Utilidades estándares del sistema". Sólo
consola básica.

Así que he montado dos discos con LVM, y estoy ajustando un script de
resguardo a colgar del crontab un poco más sofisticado que un simple
rsync.
Instalar Debian con LVM desde cero me llevó no más de 30 minutos.

Es impresionante cómo se ralentizan los procesos de lectura/escritura
a disco con RAID por 'software'.

Gracias a todos.

JAP

Re: ssh

[Freek de Kruijf]

Op maandag 12 november 2018 14:49:23 CET schreef Alan Taylor:
> Greetings,
> 
> I have an ssh problem - one user can use it successfully, another cannot. I
> have checked and rechecked permissions until I am blue in the face … At the
> moment just trying to ssh into the same machine I am on for the problem
> user (the other user can ssh successfully, both to the console machine and
> outwards to others). Agent problem ? The successful user was setup in the
> installation, the problem user was added at the command line after initial
> setup.
> 
> Log output follows, appears to fail after the preauth stage …
> 
> Any suggestions gratefully accepted
> 
> root@sirius/etc/ssh # journalctl | grep sshd | grep "Nov 12 13:45"
> Nov 12 13:45:17 sirius sshd[3155]: debug3: fd 4 is not O_NONBLOCK
> Nov 12 13:45:17 sirius sshd[3155]: debug1: Forked child 3241.
> Nov 12 13:45:17 sirius sshd[3155]: debug3: send_rexec_state: entering fd = 7
> config len 650 Nov 12 13:45:17 sirius sshd[3155]: debug3: ssh_msg_send:
> type 0
> Nov 12 13:45:17 sirius sshd[3241]: debug3: oom_adjust_restore
> Nov 12 13:45:17 sirius sshd[3155]: debug3: send_rexec_state: done
> Nov 12 13:45:17 sirius sshd[3241]: debug1: Set /proc/self/oom_score_adj to 0
> Nov 12 13:45:17 sirius sshd[3241]: debug1: rexec start in 4 out 4 newsock 4
> pipe 6 sock 7 Nov 12 13:45:17 sirius sshd[3241]: debug1: inetd sockets
> after dupping: 3, 3 Nov 12 13:45:17 sirius sshd[3241]: Connection from
> 192.168.8.3 port 39668 on 192.168.8.3 port 50400 Nov 12 13:45:17 sirius
> sshd[3241]: debug1: Client protocol version 2.0; client software version
> OpenSSH_7.4p1 Debian-10+deb9u4 Nov 12 13:45:17 sirius sshd[3241]: debug1:
> match: OpenSSH_7.4p1 Debian-10+deb9u4 pat OpenSSH* compat 0x0400 Nov 12
> 13:45:17 sirius sshd[3241]: debug1: Local version string
> SSH-2.0-OpenSSH_7.4p1 Debian-10+deb9u4 Nov 12 13:45:17 sirius sshd[3241]:
> debug1: Enabling compatibility mode for protocol 2.0 Nov 12 13:45:17 sirius
> sshd[3241]: debug2: fd 3 setting O_NONBLOCK Nov 12 13:45:17 sirius
> sshd[3241]: debug3: ssh_sandbox_init: preparing seccomp filter sandbox Nov
> 12 13:45:17 sirius sshd[3241]: debug2: Network child is on pid 3242 Nov 12
> 13:45:17 sirius sshd[3241]: debug3: preauth child monitor started Nov 12
> 13:45:17 sirius sshd[3241]: debug3: privsep user:group 117:65534 [preauth]
> Nov 12 13:45:17 sirius sshd[3241]: debug1: permanently_set_uid: 117/65534
> [preauth] Nov 12 13:45:17 sirius sshd[3241]: debug3: ssh_sandbox_child:
> setting PR_SET_NO_NEW_PRIVS [preauth] Nov 12 13:45:17 sirius sshd[3241]:
> debug3: ssh_sandbox_child: attaching seccomp filter program [preauth] Nov
> 12 13:45:17 sirius sshd[3241]: debug1: list_hostkey_types:
> ssh-ed25519,ssh-rsa,rsa-sha2-512,rsa-sha2-256 [preauth] Nov 12 13:45:17
> sirius sshd[3241]: debug3: send packet: type 20 [preauth] Nov 12 13:45:17
> sirius sshd[3241]: debug1: SSH2_MSG_KEXINIT sent [preauth] Nov 12 13:45:17
> sirius sshd[3241]: debug3: receive packet: type 20 [preauth] Nov 12
> 13:45:17 sirius sshd[3241]: debug1: SSH2_MSG_KEXINIT received [preauth] Nov
> 12 13:45:17 sirius sshd[3241]: debug2: local server KEXINIT proposal
> [preauth] Nov 12 13:45:17 sirius sshd[3241]: debug2: KEX algorithms:
> curve25519-sha256,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2
> -nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hel
> lman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha
> 256,diffie-hellman-group14-sha1 [preauth] Nov 12 13:45:17 sirius sshd[3241]:
> debug2: host key algorithms: ssh-ed25519,ssh-rsa,rsa-sha2-512,rsa-sha2-256
> [preauth] Nov 12 13:45:17 sirius sshd[3241]: debug2: ciphers ctos:
> chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@o
> penssh.com,aes256-...@openssh.com[preauth] Nov 12 13:45:17 sirius
> sshd[3241]: debug2: ciphers stoc:
> chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@o
> penssh.com,aes256-...@openssh.com[preauth] Nov 12 13:45:17 sirius
> sshd[3241]: debug2: MACs ctos:
> umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-etm@openssh.
> com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac-64@openssh.
> com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 [preauth] Nov
> 12 13:45:17 sirius sshd[3241]: debug2: MACs stoc:
> umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-etm@openssh.
> com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac-64@openssh.
> com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 [preauth] Nov
> 12 13:45:17 sirius sshd[3241]: debug2: compression ctos: none [preauth] Nov
> 12 13:45:17 sirius sshd[3241]: debug2: compression stoc: none [preauth] Nov
> 12 13:45:17 sirius sshd[3241]: debug2: languages ctos: [preauth] Nov 12
> 13:45:17 sirius sshd[3241]: debug2: languages stoc: [preauth] Nov 12
> 13:45:17 sirius sshd[3241]: debug2: first_kex_follows 0 [preauth] Nov 12
> 13:45:17 sirius sshd[3241]: debug2: reserved 0 

Re: ssh

[Andrew McGlashan]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256



On 13/11/18 12:49 am, Alan Taylor wrote:
> Greetings,
> 
> I have an ssh problem - one user can use it successfully, another 
> cannot. I have checked and rechecked permissions until I am blue in
> the face … At the moment just trying to ssh into the same machine I
> am on for the problem user (the other user can ssh successfully,
> both to the console machine and outwards to others). Agent problem
> ? The successful user was setup in the installation, the problem
> user was added at the command line after initial setup.

Maybe the initial user was added to an ssh_group and the new user
hasn't been and the ssh settings might be restricting to users in that
group?

Just an idea

Cheers
A.
-BEGIN PGP SIGNATURE-

iHUEAREIAB0WIQTJAoMHtC6YydLfjUOoFmvLt+/i+wUCW+mLPwAKCRCoFmvLt+/i
+4eEAQCQ0wU0853XzuHc3iQNp8CSFlCXfwwJtVYqFLAaR7ugpAD+Oe9pWJ9oBW1R
l+Sktgo7TK05FCczGBMOQcwbX8HcQNE=
=liaS
-END PGP SIGNATURE-

Re: ssh

[David Christensen]

Alan:

Let's keep this on-list.  I am subscribed.


So, you have installed the Debian package 'backuppc' on host 'sirius', 
and intend to use it as a BackupPC server?



The package created the group 'backuppc' and the user 'backuppc', with 
home directory '/usr/local/BackupPC'?



How were the contents of your /etc/ssh created?  The permissions don't 
match mine -- my *_key files are 0600 and everything else is 0644.



The metadata for your /usr/local/BackupPC/.ssh looks okay.


How were the contents of your /usr/local/BackupPC/.ssh created?  The 
permissions don't match mine -- my *.pub files are 0644 and everything 
else is 0600.



My client .ssh directory has 1 hard link.  Do you know why yours has 2?


There are some lines in your login attempt that look suspicious -- I 
have noted them with asterisks (*):


debug1: identity file 
/usr/local/BackupPC/.ssh/sirius_bpc-id_ed25519 type 4

*   debug1: key_load_public: No such file or directory


debug1: identity file /usr/local/BackupPC/.ssh/sirius_bpc-id_rsa type 1
*   debug1: key_load_public: No such file or directory


Doing the same test on my network produces the same messages, but the 
login works correctly.  So, I think we can ignore "key_load_public: No 
such file or directory" (?).



Comparing your 'ssh -v sirius' to testing on my network, the output 
diverges after the line:


Server accepts key: pkalg ssh-rsa blen 535

Mine then says:

debug1: Authentication succeeded (publickey).
Authenticated to cvs ([192.168.1.25]:22).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessi...@openssh.com
debug1: Entering interactive session.
debug1: pledge: network
debug1: client_input_global_request: rtype hostkeys...@openssh.com 
want_reply 0

debug1: Sending environment.
debug1: Sending env LANG = C


Localization and UTF-8 have caused me problems in the past, so I have 
the following line in my .profile.  This may or may not help you:


export LANG=C


The entries in your authorized_keys file look different than mine -- 
yours contain ' Generated on 181113.1203 for' near the end of both 
matching entries.  Do your *.pub files have this phrase?  How was your 
authorized_keys created?



After a successful login, my auth.log says:

Nov 12 22:49:36 dipsy sshd[3395]: Accepted publickey for dpchrist 
from 192.168.1.142 port 39164 ssh2: RSA 
SHA256:BAg+ZqGUnRYXU0QssQkuaBqzjxsgyjIKJeoZ8H5SG9E
Nov 12 22:49:36 dipsy sshd[3395]: pam_unix(sshd:session): session 
opened for user dpchrist by (uid=0)



I would reset the modes of your SSH client files as backuppc@sirius:

$ cd /usr/local/BackupPC/.ssh

$ chmod 0600 *

$ chmod 0644 *.pub


I would reset the modes of your SSH server files as root@sirius:

# cd /etc/ssh

# chmod 0644 *

# chmod 0600 *_key


Then try 'ssh -v sirius' and look at auth.log.


David



On 11/12/18 8:34 PM, Alan Taylor wrote:

Hello,

Output from several suggestions:

Permissions (backuppc is the user having problems) :

backuppc@sirius:~$ ls -ld /usr/local/BackupPC
drwxr-xr-x 6 backuppc backuppc 4096 Nov 13 12:12 /usr/local/BackupPC
backuppc@sirius:~$ ls -ld /usr/local/BackupPC/.ssh
drwx-- 2 backuppc backuppc 4096 Nov 13 12:08 /usr/local/BackupPC/.ssh
backuppc@sirius:~$ ls -l /usr/local/BackupPC/.sshtotal 28
-rw--- 1 backuppc backuppc 1790 Nov 13 12:04 authorized_keys
-rw-r- 1 backuppc backuppc 2240 Nov 13 12:02 config
-rw-r--r-- 1 backuppc backuppc  142 Nov 13 12:08 known_hosts
-rw--- 1 backuppc backuppc  484 Nov 13 12:03 sirius_bpc-id_ed25519
-rw-r- 1 backuppc backuppc  126 Nov 13 12:03 sirius_bpc-id_ed25519.pub
-rw--- 1 backuppc backuppc 3479 Nov 13 12:04 sirius_bpc-id_rsa
-rw-r- 1 backuppc backuppc  770 Nov 13 12:04 sirius_bpc-id_rsa.pub
backuppc@sirius:~$
backuppc@sirius:~$ ls -la /etc/ssh
drwxr-xr-x   2 root root   4096 Nov 13 12:04 .
drwxr-xr-x 131 root root  12288 Nov 13 12:05 ..
-rw-r--r--   1 root root 511915 Nov 13 12:02 moduli
-rw-r--r--   1 root root 553122 Aug 21 11:14 moduli.dist
-rw---   1 root root888 Nov 13 12:03 sirius_alan-authorized_keys
-rw-rw   1 root root896 Nov 13 12:04 sirius_bpc-authorized_keys
-rw-r--r--   1 root root   2830 Nov 13 12:02 ssh_config
-rw-r--r--   1 root root   1723 Aug 21 11:14 ssh_config.dist
-rw-r--r--   1 root root   4239 Nov 13 12:02 sshd_config
-rw-r--r--   1 root root   3298 Aug 21 11:14 sshd_config.dist
-rw---   1 root root432 Nov 13 12:03 ssh_host_ed25519_key
-rw-r-   1 root root117 Nov 13 12:03 ssh_host_ed25519_key.pub
-rw---   1 root root   3243 Nov 13 12:03 ssh_host_rsa_key
-rw-r-   1 root root761 Nov 13 12:03 ssh_host_rsa_key.pub
backuppc@sirius:~$
These permissions are identical to the user that works.

Output from David's troubleshooting :

As backuppc (problem user):

backuppc@sirius:~$ whoami
backuppc

Re: ssh

[john doe]

On 11/12/2018 2:49 PM, Alan Taylor wrote:
> Greetings,
> 
> I have an ssh problem - one user can use it successfully, another cannot. I 
> have checked and rechecked permissions until I am blue in the face …
> At the moment just trying to ssh into the same machine I am on for the 
> problem user (the other user can ssh successfully, both to the console 
> machine and outwards to others).
> Agent problem ? The successful user was setup in the installation, the 
> problem user was added at the command line after initial setup.
> 
> Log output follows, appears to fail after the preauth stage …
> 
> Any suggestions gratefully accepted
> 
> root@sirius/etc/ssh # journalctl | grep sshd | grep "Nov 12 13:45"
> Nov 12 13:45:17 sirius sshd[3155]: debug3: fd 4 is not O_NONBLOCK
> Nov 12 13:45:17 sirius sshd[3155]: debug1: Forked child 3241.
> Nov 12 13:45:17 sirius sshd[3155]: debug3: send_rexec_state: entering fd = 7 
> config len 650
> Nov 12 13:45:17 sirius sshd[3155]: debug3: ssh_msg_send: type 0
> Nov 12 13:45:17 sirius sshd[3241]: debug3: oom_adjust_restore
> Nov 12 13:45:17 sirius sshd[3155]: debug3: send_rexec_state: done
> Nov 12 13:45:17 sirius sshd[3241]: debug1: Set /proc/self/oom_score_adj to 0
> Nov 12 13:45:17 sirius sshd[3241]: debug1: rexec start in 4 out 4 newsock 4 
> pipe 6 sock 7
> Nov 12 13:45:17 sirius sshd[3241]: debug1: inetd sockets after dupping: 3, 3
> Nov 12 13:45:17 sirius sshd[3241]: Connection from 192.168.8.3 port 39668 on 
> 192.168.8.3 port 50400
> Nov 12 13:45:17 sirius sshd[3241]: debug1: Client protocol version 2.0; 
> client software version OpenSSH_7.4p1 Debian-10+deb9u4
> Nov 12 13:45:17 sirius sshd[3241]: debug1: match: OpenSSH_7.4p1 
> Debian-10+deb9u4 pat OpenSSH* compat 0x0400
> Nov 12 13:45:17 sirius sshd[3241]: debug1: Local version string 
> SSH-2.0-OpenSSH_7.4p1 Debian-10+deb9u4
> Nov 12 13:45:17 sirius sshd[3241]: debug1: Enabling compatibility mode for 
> protocol 2.0
> Nov 12 13:45:17 sirius sshd[3241]: debug2: fd 3 setting O_NONBLOCK
> Nov 12 13:45:17 sirius sshd[3241]: debug3: ssh_sandbox_init: preparing 
> seccomp filter sandbox
> Nov 12 13:45:17 sirius sshd[3241]: debug2: Network child is on pid 3242
> Nov 12 13:45:17 sirius sshd[3241]: debug3: preauth child monitor started
> Nov 12 13:45:17 sirius sshd[3241]: debug3: privsep user:group 117:65534 
> [preauth]
> Nov 12 13:45:17 sirius sshd[3241]: debug1: permanently_set_uid: 117/65534 
> [preauth]
> Nov 12 13:45:17 sirius sshd[3241]: debug3: ssh_sandbox_child: setting 
> PR_SET_NO_NEW_PRIVS [preauth]
> Nov 12 13:45:17 sirius sshd[3241]: debug3: ssh_sandbox_child: attaching 
> seccomp filter program [preauth]
> Nov 12 13:45:17 sirius sshd[3241]: debug1: list_hostkey_types: 
> ssh-ed25519,ssh-rsa,rsa-sha2-512,rsa-sha2-256 [preauth]
> Nov 12 13:45:17 sirius sshd[3241]: debug3: send packet: type 20 [preauth]
> Nov 12 13:45:17 sirius sshd[3241]: debug1: SSH2_MSG_KEXINIT sent [preauth]
> Nov 12 13:45:17 sirius sshd[3241]: debug3: receive packet: type 20 [preauth]
> Nov 12 13:45:17 sirius sshd[3241]: debug1: SSH2_MSG_KEXINIT received [preauth]
> Nov 12 13:45:17 sirius sshd[3241]: debug2: local server KEXINIT proposal 
> [preauth]
> Nov 12 13:45:17 sirius sshd[3241]: debug2: KEX algorithms: 
> curve25519-sha256,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1
>  [preauth]
> Nov 12 13:45:17 sirius sshd[3241]: debug2: host key algorithms: 
> ssh-ed25519,ssh-rsa,rsa-sha2-512,rsa-sha2-256 [preauth]
> Nov 12 13:45:17 sirius sshd[3241]: debug2: ciphers ctos: 
> chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com[preauth]
> Nov 12 13:45:17 sirius sshd[3241]: debug2: ciphers stoc: 
> chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com[preauth]
> Nov 12 13:45:17 sirius sshd[3241]: debug2: MACs ctos: 
> umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
>  [preauth]
> Nov 12 13:45:17 sirius sshd[3241]: debug2: MACs stoc: 
> umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
>  [preauth]
> Nov 12 13:45:17 sirius sshd[3241]: debug2: compression ctos: none [preauth]
> Nov 12 13:45:17 sirius sshd[3241]: debug2: compression stoc: none [preauth]
> Nov 12 13:45:17 sirius sshd[3241]: debug2: languages ctos: [preauth]
> Nov 12 13:45:17 sirius sshd[3241]: debug2: languages stoc: [preauth]
> Nov 12 13:45:17 sirius sshd[3241]: debug2: first_kex_follows 0 [preauth]
> Nov 12 13:45:17 sirius sshd[3241]: debug2: reserved 

Re: Lire ses logs rapidement de façon efficace

[G2PC]

> Une solution pas facile facile à mettre en oeuvre mais efficace une
> fois la solution mise en place,  le triplet "elasticsearch,  logstach
> et kibana"

C'est  noté :
https://www.visionduweb.eu/wiki/index.php?title=Sommaire_S%C3%A9curit%C3%A9#Aller_plus_loin_avec_les_logs

Re: portable CD players

[rhkramer]

On Monday, November 12, 2018 08:35:23 AM Greg Wooledge wrote:
> On Sat, Nov 10, 2018 at 10:47:11AM -0500, rhkra...@gmail.com wrote:
> > IIRC, a CD holds a maximum of 80 minutes .wav sound.  (Around 800MB,
> > about 1 MB per minute).  A 4 GB holds way more than that in .mp3,
> > although a figure doesn't come to mind at the moment -- maybe more on
> > the order of 40 hours of sound.  And, it is reprogrammable.
> 
> For starters, your "1 MB per minute" math is off.  Even using the numbers
> you showed, that's 10 MB per minute.

Oops, yes, you are correct  (sometimes I write before I think ;-)

And thanks for all the additional good information that you provided!

Re: ssh

[rhkramer]

On Monday, November 12, 2018 09:16:37 AM Andrew McGlashan wrote:
> On 13/11/18 12:49 am, Alan Taylor wrote:
> > Greetings,
> > 
> > I have an ssh problem - one user can use it successfully, another
> > cannot. I have checked and rechecked permissions until I am blue in
> > the face … At the moment just trying to ssh into the same machine I
> > am on for the problem user (the other user can ssh successfully,
> > both to the console machine and outwards to others). Agent problem
> > ? The successful user was setup in the installation, the problem
> > user was added at the command line after initial setup.
> 
> Maybe the initial user was added to an ssh_group and the new user
> hasn't been and the ssh settings might be restricting to users in that
> group?

Thank you for snipping appropriately!

Re: ssh

[Andrew McGlashan]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Okay, show us the user's home directory permissions and that of their
own .ssh directory please.

Also, the permissions of the authorized_keys file.

And there are no typos in /etc/group for the users allowed by
"AllowUsers" ?

Nothing in the sshd_config that overrides the "AllowUsers" entry?

A.
-BEGIN PGP SIGNATURE-

iHUEAREIAB0WIQTJAoMHtC6YydLfjUOoFmvLt+/i+wUCW+mPOQAKCRCoFmvLt+/i
+533AP93gMfjhlyvnaT+pih96PYsN/piqu8VjWxTPF33/quytAD/fr5UxgOChEWS
Q4NAvP7746IVVUX5/o46V2bH+eAfnWQ=
=nN0Z
-END PGP SIGNATURE-

Re: Consulta sobre Raid.

[Galvatorix Torixgalva]

Hola,

nada más lejos de mi intención desinformar.

Sucede que hace tiempo tuve la suerte de usar un equipo con dos discos
duros y aproveché para realizar unas pruebas con raid.

Lo que hice en la contestación fue intentar ponerme en el mejor de los
casos y también en el peor de los casos.

Y sí, creo que he leído todos los mensajes del hilo.

Saludos

El lun., 12 de noviembre de 2018 1:12 p. m., Matias Mucciolo <
mmucci...@suteba.org.ar> escribió:

>
> On Saturday, November 10, 2018 4:30:30 PM -03 Galvatorix Torixgalva wrote:
> > Hola,
> >
> > Creo, y digo creo, que o consigues todos los discos del raid. o te
> > olvidas.
> >
> > Raid tiene cosas positivas y cosas negativas. Las positivas son muy
> > positivas y las negativas son muy negativas.
> >
> > Podrías consultar con empresas especializadas si es posible, pero algo
> así
> > no creo que sea barato.
> >
> > Saludos
>
> Por favor no des-informes a la gente..(y lee todo el hilo en lo posible)
> un raid 1 se puede montar sin problemas con solo
> tener un disco.
>
> Robert pudiste montar ver lvm ?
>
> saludos.
> Matias.
>
>

Re: Archiving content of a directory on a DVD-R.

[peter]

On Wed, Nov 07, 2018 at 01:52:13PM -0800, pe...@easthope.ca wrote:
> > My backup procedures are shell functions 
> > rather than scripts

*   From: Greg Wooledge 
*   Date: Thu, 8 Nov 2018 08:18:15 -0500
> That's pretty bizarre.  I don't see what advantage that gives you over
> simply putting the commands in a script so that you can run something like
> "sudo backup" on demand.

How are multiple commands defined in one file?  Then invoke?
sudo backup1
sudo backup2
sudo backup3

Thanks,  ... Peter E.



-- 
Message composed and transmitted by software designed to avoid the 
need, overhead and vulnerability of antivirus software.

123456789 123456789 123456789 123456789 123456789 123456789 123456789
Tel: +1 360 639 0202  +1 
http://easthope.ca/Peter.html  Bcc: peter at easthope. ca

Re: heads up: timidity causes pulseaudio to not find sound cards

[Jochen Spieker]

Eric S Fraga:
> 
> I recently did an 'apt update; apt upgrade' on my desktop which is
> running testing (aka buster).  Doing so led to my losing sound through
> any application that relies on pulseaudio, e.g. firefox.  I could still
> use console based tools (e.g. mocp) to listen to music but pulseaudio
> could not find my default built-in sound card, only the nvidia card
> which provides sound through HDMI.

I had a similar issue, but in my case it was just the order of the audio
devices that was shuffled around:

$ cat /proc/asound/cards
 0 [HDMI   ]: HDA-Intel - HDA Intel HDMI
  HDA Intel HDMI at 0xe063 irq 48
 1 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0xe0634000 irq 46

I can only assume that previously the PCH device was 0 and the HDMI
device was 1. In any case, alsamixer did not show any volume controls
anymore and applications like mplayer, which produce sensible error
output, reported that they failed to find a proper audio device.

The solution was simple:

$ grep snd_ /etc/modprobe.d/local.conf
options snd_hda_intel index=0
options snd_hda_codec_hdmi index=1

That and a reboot fixed it.

J.
-- 
I eat meat and am concerned about bugs which are resistant to
antibiotics.
[Agree]   [Disagree]
 


signature.asc
Description: PGP signature

Re: P2V Convertendo maquina a quente com raid software

[Leandro Guimarães Faria Corcete DUTRA]

Le lundi 12 novembre 2018 à 15:54 -0200, Anderson Bertling a écrit :
> edito os arquivos fstab e grub

Edita como?  De que valores para que valores?

>  mas quando subo a maquina aparece erro,

Que erro, para que comando com que valores de configuração nos arquivos
acima?

Ajude-nos a ajudar-te: mensagem em texto simples (sem HTML nem
ETF), pontuada e completa.


-- 
skype:leandro.gfc.dutra?chat  Yahoo!: ymsgr:sendIM?lgcdutra
+55 (61) 3546 7191  gTalk: xmpp:leand...@jabber.org
+55 (61) 9302 2691ICQ/AIM: aim:GoIM?screenname=61287803
BRAZIL GMT−3  MSN: msnim:chat?contact=lean...@dutra.fastmail.fm

Re: Archiving content of a directory on a DVD-R.

[Greg Wooledge]

On Mon, Nov 12, 2018 at 01:13:14PM -0800, pe...@easthope.ca wrote:
> How are multiple commands defined in one file?  Then invoke?
> sudo backup1
> sudo backup2
> sudo backup3

Just put all the commands in one script, for example:

#!/bin/sh
backup1 &&
backup2 &&
backup3


Then run "sudo /the/backupscript".  If it's in a directory in your PATH,
you can simply do "sudo backupscript".

Of course, your example is so entirely obfuscated and genericized that
it's meaningless.  You can't even demonstrate anything with it.

Here's the backup script I use at home, with only one piece of information
hidden.  It's not elegant.  It's simply what I've got.

It is named /usr/local/bin/backup.  When I want to run it, I type
"sudo backup".

#!/bin/bash

cd /backup || exit
today=$(date +%Y%m%d)

if [ -e /hd/.hd ]; then
( cd / && rsync -av --delete etc home usr/local /hd/titan/ )
( cd /stuff && rsync -av --delete * /hd/ )
else
echo "/hd not mounted"
fi

( cd /etc && find . -print0 |
cpio -o -0 | gzip > "/backup/compress/backup.$HOSTNAME.etc.$today" )

( export RSYNC_RSH='ssh -p [REDACTED]';
  cd remote && rsync -av --delete r...@remote.wooledge.org:{/etc,/var/moin} . )

( cd remote && find . -print0 |
cpio -o -0 | gzip > "/backup/compress/backup.remote.$today" )

( cd /home && find . \( -type d -name .cache \) -prune -o -print0 |
cpio -o -0 | gzip > "/backup/compress/backup.$HOSTNAME.home.$today" )

find compress -type f -mtime +4 -delete
( cd compress && mkisofs -o ../image . )

ls -ld image
read -p "Write to DVD? [y] " yn
case $yn in ''|[Yy]|[Yy]es) : ;; *) exit ;; esac
cdrecord -v image

Re: pushd/popd

[David Wright]

On Mon 12 Nov 2018 at 08:40:15 (-0500), Greg Wooledge wrote:
> On Sat, Nov 10, 2018 at 11:58:53PM -0600, David Wright wrote:
> > BTW whenever I change directory in scripts, I make sure that I'm in a
> > subshell by using ( and ), which guarantees that I get back to the
> > same directory however the script finishes.
> 
> Depends on the script.  For scripts that change directory more than
> once (e.g. a software building script that runs "make" in several
> directories, one by one), I concur.  That is sound advice.
> 
> For a script that only changes directory once and then does everything
> from that directory (e.g. a wrapper), a subshell may be the exact
> opposite of what's wanted.  In such cases, you would simply do
> "cd /some/where || exit" at the top of the script.

Yes, quite a few of my bin/ scripts are like that. But in the aside,
I was really talking about scripts that are contained in OP's shell
functions where, if you pushd but then crash out for whatever reason
without doing the matching popd, you get left in a different directory
from the one you started in. Perhaps s/whenever/when/ and qualifications.

Cheers,
David.

Re: Mystery interface reported by ip.

[peter]

*   From: Reco 
*   Date: Fri, 9 Nov 2018 19:56:24 +0300
> Ok, let's do it the hard way.
> 
> udevadm info /sys/class/net/LocLCS218301788

peter@joule:~$ udevadm info /sys/class/net/LocLCS218301788
P: /devices/pci:00/:00:1e.0/:02:08.0/net/LocLCS218301788
E: DEVPATH=/devices/pci:00/:00:1e.0/:02:08.0/net/LocLCS218301788
E: ID_BUS=pci
E: ID_MODEL_FROM_DATABASE=82562EZ 10/100 Ethernet Controller
E: ID_MODEL_ID=0x1050
E: ID_NET_DRIVER=e100
E: ID_NET_LINK_FILE=/lib/systemd/network/99-default.link
E: ID_NET_NAME_MAC=enx0007e978a8b0
E: ID_NET_NAME_PATH=enp2s8
E: ID_OUI_FROM_DATABASE=Intel Corporation
E: ID_PATH=pci-:02:08.0
E: ID_PATH_TAG=pci-_02_08_0
E: ID_PCI_CLASS_FROM_DATABASE=Network controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller
E: ID_VENDOR_FROM_DATABASE=Intel Corporation
E: ID_VENDOR_ID=0x8086
E: IFINDEX=2
E: INTERFACE=LocLCS218301788
E: SUBSYSTEM=net
E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/LocLCS218301788
E: TAGS=:systemd:
E: USEC_INITIALIZED=1550444

> udevadm trigger /sys/class/net/LocLCS218301788

peter@joule:~$ udevadm trigger /sys/class/net/LocLCS218301788
[no output]

> udevadm info /sys/class/net/rename4

peter@joule:~$ udevadm info /sys/class/net/rename4
Unknown device, --name=, --path=, or absolute path in /dev/ or /sys expected.

> udevadm trigger /sys/class/net/rename4

peter@joule:~$ udevadm trigger /sys/class/net/rename4
unable to open the device '/sys/class/net/rename4'

Thanks,   ... Peter E.

-- 
Message composed and transmitted by software designed to avoid the 
need, overhead and vulnerability of antivirus software.

123456789 123456789 123456789 123456789 123456789 123456789 123456789
Tel: +1 360 639 0202  +1 
http://easthope.ca/Peter.html  Bcc: peter at easthope. ca

P2V Convertendo maquina a quente com raid software

[Anderson Bertling]

 Boa tarde a todos, estou com problemas para converter uma maquina real em
virtual pois a mesma possui raid em software, a conversão se encerra aos
97%  edito os arquivos fstab e grub mas quando subo a maquina aparece erro,
alguém já fez essa ação de conversão?  não consigo subir a vm  agradeço
qualquer ajuda
md0 to sda1 /
md1 to sdb1 swap


-- 
Att

Anderson Bertling