AdminSysGNULinux

Outils pour utilisateurs

Outils du site

Piste : • blog
blog

Table des matières

8 billet(s) pour mars 2026

Notes conteneurs oras artifact OCI2026/03/23 21:13Jean-Baptiste
Notes podman secret2026/03/23 15:10Jean-Baptiste
Notes ansible podman2026/03/23 14:08Jean-Baptiste
Notes podman volume2026/03/23 14:00Jean-Baptiste
Find list - Trouver des fichiers à partir d'une liste2026/03/18 14:32Jean-Baptiste
AWX inventaire vault2026/03/17 18:04Jean-Baptiste
AWX - Configuration git en local (sans serveur web)2026/03/05 16:24Jean-Baptiste
OpenSMTP2026/03/03 16:58Jean-Baptiste

Notes vidéo - logiciels édition

éditeurs de vidéo non linéaires :

2025/03/24 15:06
,

Notes Varnish

Varnish

Voir : 

apt-get install varnish varnish-doc

/etc/systemd/system/varnish.service.d/plop.conf 

# To add or override specific settings for the Varnish service, place a copy of
# this file in /etc/systemd/system/varnish.service.d/ with a ".conf" suffix,
# and edit to taste.  See man:systemd.directives for what you can change.
#
# To activate, run:
# * "systemctl daemon-reload"
# * "systemctl restart varnish"
 
# Add a documentation link to my own system documentation
[Unit]
Documentation=https://doc.example.com/client_a/varnish_service
 
[Service]
# Clear existing ExecStart= (required)
ExecStart=
# Set a new ExecStart=
ExecStart=/usr/sbin/varnishd -j unix,user=vcache -F -a :80 -T localhost:8080 -f /etc/varnish/default.vcl -S /etc/varnish/secret -s malloc,16g

/etc/varnish/default.vcl 

#
# This is an example VCL file for Varnish.
#
# It does not do anything by default, delegating control to the
# builtin VCL. The builtin VCL is called when there is no explicit
# return statement.
#
# See the VCL chapters in the Users Guide at https://www.varnish-cache.org/docs/
# and https://www.varnish-cache.org/trac/wiki/VCLExamples for more examples.
 
# Marker to tell the VCL compiler that this VCL has been adapted to the
# new 4.0 format.
vcl 4.0;
 
# Default backend definition. Set this to point to your content server.
backend default {
    .host = "127.0.0.1";
    .port = "8080";
}
 
sub vcl_recv {
    # Happens before we check if we have this in cache already.
    #
    # Typically you clean up the request here, removing cookies you don't need,
    # rewriting the request, etc.
}
 
sub vcl_backend_response {
    # Happens after we have read the response headers from the backend.
    #
    # Here you clean the response headers, removing silly Set-Cookie headers
    # and other mistakes your backend does.
}
 
sub vcl_deliver {
    # Happens when we have all the pieces we need, and are about to send the
    # response to the client.
    #
    # You can do accounting or modifying the final object here.
}

VCL configuration Varnish will automatically append to your VCL file during compilation/loading :
/usr/share/doc/varnish/examples/builtin.vcl.gz

Deux services :

  • varnish
  • varnishncsa (Display Varnish logs in Apache / NCSA combined log format)
mkdir /lib/systemd/system/varnish.service.d
#cp -p /lib/systemd/system/varnish.service /lib/systemd/system/varnish.service.d/plop.conf
cp -p /usr/share/doc/varnish/examples/systemd/varnish.commandline.conf /lib/systemd/system/varnish.service.d/plop.conf
vim !$

Varnish admin CLI 

#varnishadm -S /etc/varnish/secret -T 127.0.0.1:6082
varnishadm -S /etc/varnish/secret -T 127.0.0.1:6082

Reload Varnish

Reload Varnish VCL without losing cache data

/usr/local/bin/varnish_reload.sh 

#!/bin/bash
 
TIME=$(date +%s)
varnishadm vcl.load r_$TIME /etc/varnish/default.vcl
varnishadm vcl.use r_$TIME

/lib/systemd/system/varnish.service.d/reload.conf 

[Service]
ExecReload=/usr/local/bin/varnish_reload.sh
chmod +x /usr/local/bin/varnish_reload.sh
systemctl daemon-reload
 
# Now you can reload with :
#systemctl reload varnish

VCL

Voir :

VCL

Actions coté client et backend :

  • fail (Transition vers vcl_synth)

Actions coté client :

  • synth (synthérique, Transition vers vcl_synth
  • pass (OK, ne pas utiliser le cache, eveltuelle transition vers vcl_pass)
  • pipe (bypass Varnish, Transition vers vcl_pipe)
  • restart

Actions coté backend :

  • abandon (Unless the backend request was a background fetchTransition vers vcl_synth)

Les Built-in subroutines coté client :

  • vcl_recv (point d'entrée)
  • vcl_pipe (bypass)
  • etc…

Debug

varnishd -d -f /etc/varnish/default.vcl

Pour avoir la command de lancement du daemon avec les arguments : 

systemctl status varnish

On enlève le -F et on le remplace par un -d 

#sudo /usr/sbin/varnishd -j unix,user=vcache -d -F -a :6081 -T localhost:6082 -f /etc/varnish/default.vcl -S /etc/varnish/secret -s malloc,256m
sudo /usr/sbin/varnishd -j unix,user=vcache -d -d -a :6081 -T localhost:6082 -f /etc/varnish/default.vcl -S /etc/varnish/secret -s malloc,256m

Tapez start pour lancer le service

Vérifier la syntax du fichier VCL 

varnishd -Cf /etc/varnish/default.vcl

Changer les headers 

sub vcl_deliver {
        unset resp.http.Via;
        #unset resp.http.X-Powered-By;
        unset resp.http.X-Varnish;
        #unset resp.http.Age;
        unset resp.http.Server;
}
Purge du cache
curl -X PURGE -H "host: www.example.com" "www.example.com/foo"
 
# HTTPie
http PURGE "www.example.com/foo"
Bloquer (BAN)
varnishadm ban req.http.host == example.com '&&' req.url '~' '\\.png$

Autres

Architecture : 

varnishlog -g raw
varnishstat -l
varnishstat -1 -n varnish_instancename
sudo varnishlog -n varnish_instancename -q 'ReqHeader ~ "Host: plop.fr"'

purge : 

sub vcl_recv {
  # Add a unique header containing the client address
  remove req.http.X-Forwarded-For;
  set    req.http.X-Forwarded-For = client.ip;
  # [...]
}
2025/03/24 15:06
, , ,

Notes vagrant

Install du module pour KVM/Libvirt
Voir https://github.com/vagrant-libvirt/vagrant-libvirt 

sudo apt-get install libxslt-dev libxml2-dev libvirt-dev zlib1g-dev ruby-dev
 
vagrant plugin install vagrant-libvirt

Test avec CentOS7 

vagrant init centos/7
 
# Semble être ignoré. ''--provider=libvirt'' Nécessaire
#export VAGRANT_DEFAULT_PROVIDER=libvirt
 
export LIBVIRT_DEFAULT_URI="qemu:///system"
 
vagrant up --provider=libvirt

Pb

vagrant up  --provider=libvirt
Bringing machine 'default' up with 'libvirt' provider...
/home/jean/.vagrant.d/gems/gems/fog-libvirt-0.0.3/lib/fog/libvirt/requests/compute/list_volumes.rb:32:in `info': Call to virStorageVolGetInfo failed: Storage volume not found: no storage vol with matching path '/tmp/systemd-private-04e45e030a974efa97ce503d7fb920ce-cups.service-AQNzoq' (Libvirt::RetrieveError)
        from /home/jean/.vagrant.d/gems/gems/fog-libvirt-0.0.3/lib/fog/libvirt/requests/compute/list_volumes.rb:32:in `volume_to_attributes'
        from /home/jean/.vagrant.d/gems/gems/fog-libvirt-0.0.3/lib/fog/libvirt/requests/compute/list_volumes.rb:10:in `block (2 levels) in list_volumes'
        from /home/jean/.vagrant.d/gems/gems/fog-libvirt-0.0.3/lib/fog/libvirt/requests/compute/list_volumes.rb:9:in `each'
        from /home/jean/.vagrant.d/gems/gems/fog-libvirt-0.0.3/lib/fog/libvirt/requests/compute/list_volumes.rb:9:in `block in list_volumes'
        from /home/jean/.vagrant.d/gems/gems/fog-libvirt-0.0.3/lib/fog/libvirt/requests/compute/list_volumes.rb:44:in `block in raw_volumes'
        from /home/jean/.vagrant.d/gems/gems/fog-libvirt-0.0.3/lib/fog/libvirt/requests/compute/list_volumes.rb:42:in `each'
        from /home/jean/.vagrant.d/gems/gems/fog-libvirt-0.0.3/lib/fog/libvirt/requests/compute/list_volumes.rb:42:in `raw_volumes'
        from /home/jean/.vagrant.d/gems/gems/fog-libvirt-0.0.3/lib/fog/libvirt/requests/compute/list_volumes.rb:8:in `list_volumes'
        from /home/jean/.vagrant.d/gems/gems/fog-libvirt-0.0.3/lib/fog/libvirt/models/compute/volumes.rb:11:in `all'
        from /home/jean/.vagrant.d/gems/gems/vagrant-libvirt-0.0.33/lib/vagrant-libvirt/action/handle_box_image.rb:63:in `block in call'
        from /home/jean/.vagrant.d/gems/gems/vagrant-libvirt-0.0.33/lib/vagrant-libvirt/action/handle_box_image.rb:60:in `synchronize'
        from /home/jean/.vagrant.d/gems/gems/vagrant-libvirt-0.0.33/lib/vagrant-libvirt/action/handle_box_image.rb:60:in `call'
        from /usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
        from /usr/lib/ruby/vendor_ruby/vagrant/action/builtin/handle_box.rb:56:in `call'
        from /usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
        from /home/jean/.vagrant.d/gems/gems/vagrant-libvirt-0.0.33/lib/vagrant-libvirt/action/handle_storage_pool.rb:50:in `call'
        from /usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
        from /home/jean/.vagrant.d/gems/gems/vagrant-libvirt-0.0.33/lib/vagrant-libvirt/action/set_name_of_domain.rb:35:in `call'
        from /usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
        from /usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:95:in `block in finalize_action'
        from /usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
        from /usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
        from /usr/lib/ruby/vendor_ruby/vagrant/action/builder.rb:116:in `call'
        from /usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:66:in `block in run'
        from /usr/lib/ruby/vendor_ruby/vagrant/util/busy.rb:19:in `busy'
        from /usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:66:in `run'
        from /usr/lib/ruby/vendor_ruby/vagrant/action/builtin/call.rb:53:in `call'
        from /usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
        from /usr/lib/ruby/vendor_ruby/vagrant/action/builtin/config_validate.rb:25:in `call'
        from /usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
        from /usr/lib/ruby/vendor_ruby/vagrant/action/builder.rb:116:in `call'
        from /usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:66:in `block in run'
        from /usr/lib/ruby/vendor_ruby/vagrant/util/busy.rb:19:in `busy'
        from /usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:66:in `run'
        from /usr/lib/ruby/vendor_ruby/vagrant/machine.rb:196:in `action_raw'
        from /usr/lib/ruby/vendor_ruby/vagrant/machine.rb:173:in `block in action'
        from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:440:in `lock'
        from /usr/lib/ruby/vendor_ruby/vagrant/machine.rb:161:in `call'
        from /usr/lib/ruby/vendor_ruby/vagrant/machine.rb:161:in `action'
        from /usr/lib/ruby/vendor_ruby/vagrant/batch_action.rb:82:in `block (2 levels) in run'
Solution

https://kushaldas.in/posts/storage-volume-error-in-libvirt-with-vagrant.html 

virsh pool-list
 Name                 State      Autostart 
-------------------------------------------
 default              active     yes       
 presseed             active     yes       
 tmp                  active     yes 
virsh pool-refresh tmp
virsh pool-refresh default
Connexion à la machine
vagrant ssh-config >> ~/.ssh/config
2025/03/24 15:06
, , ,

Notes userhelper - usermode

userhelper - usermode

Voir :

Voir aussi :

usermode contains the userhelper program, which can be used to allow configured programs to be run with superuser privileges by ordinary users, and several graphical tools for users:

  • userinfo allows users to change their finger information.
  • usermount lets users mount, unmount, and format filesystems.
  • userpasswd allows users to change their passwords.
sudo /usr/sbin/userhelper -t -w subscription-manager identity

/etc/security/console.apps/config-util 

USER=root
UGROUPS=wheel

/etc/security/console.apps/subscription-manager 

USER=root
PROGRAM=/usr/sbin/subscription-manager
SESSION=true
# ls -l /usr/bin/subscription-manager
lrwxrwxrwx. 1 root root 22 Feb 23 07:16 /usr/bin/subscription-manager -> /usr/bin/consolehelper

# grep '^PROGRAM=' /etc/security/console.apps/subscription-manager
PROGRAM=/usr/sbin/subscription-manager

Test

/etc/pam.d/sleep 

#%PAM-1.0
auth            include         config-util
account         include         config-util
session         include         config-util

ou

/etc/pam.d/sleep 

#%PAM-1.0
auth       sufficient   pam_rootok.so
auth required pam_warn.so
auth required pam_deny.so
auth       include      system-auth
account    include      system-auth
password   include      system-auth
session    include      system-auth

/etc/security/console.apps/sleep 

USER=root
#UGROUPS=wheel
PROGRAM=/usr/bin/sleep
SESSION=true
#KEEP_ENV_VARS=http_proxy,ftp_proxy
#FALLBACK=yes
/usr/sbin/userhelper -t -w sleep 1
2025/03/24 15:06
, ,

Notes uptime reboot shutdown stime

Voir les fichiers :

  • /var/log/auth.log
  • /var/log/secure
  • /var/log/audit/audit.log
# uptime 
 15:00:24 up  3:15,  5 users,  load average: 0.39, 0.45, 0.50

# ps -p 1 -o stime
STIME
11:44

# who -b
         démarrage système 2018-11-30 11:44
        
# lastb
         tty1                          Fri Nov 30 11:51 - 11:51  (00:00)    

btmp begins Fri Nov 30 11:51:28 2018
 

# last reboot
# last -aiF
# last -a --dns
# last -x
# last -x shutdown reboot root
# last -5 shutdown reboot root


$ uptime -s
2018-11-30 08:01:03

Auditd aureport

Voir : Notes auditd 

# aureport -ts 30/11/2018 11:30:00 -te 30/11/2018 11:45:00 -e -i

Event Report
===================================
# date time event type auid success
===================================
1. 30/11/2018 11:35:39 1272 CRYPTO_SESSION user1 yes
2. 30/11/2018 11:35:39 1273 CRYPTO_SESSION user1 yes
3. 30/11/2018 11:35:40 1274 CRYPTO_KEY_USER user1 yes
4. 30/11/2018 11:35:40 1275 CRYPTO_KEY_USER user1 yes
5. 30/11/2018 11:44:03 1276 SYSTEM_RUNLEVEL unset yes
6. 30/11/2018 11:44:03 1277 SYSTEM_SHUTDOWN unset yes
7. 30/11/2018 11:44:06 1281 CRYPTO_KEY_USER unset yes
8. 30/11/2018 11:44:06 1282 CRYPTO_KEY_USER unset yes
9. 30/11/2018 11:44:06 1283 USER_END user1 yes


# aureport -ts 30/11/2018 11:42:00 -te 30/11/2018 11:45:00 -tm

Terminal Report
====================================
# date time term host exe auid event
====================================
1. 30/11/2018 11:44:03 ? ? /sbin/shutdown -1 1276
2. 30/11/2018 11:44:03 ? ? /sbin/shutdown -1 1277
3. 30/11/2018 11:44:06 ? ? /usr/sbin/sshd -1 1281
4. 30/11/2018 11:44:06 ? ? /usr/sbin/sshd -1 1282
5. 30/11/2018 11:44:06 ssh 192.168.2.21 /usr/sbin/sshd 5005 1283
6. 30/11/2018 11:44:06 ssh 192.168.2.21 /usr/sbin/sshd 5005 1284
7. 30/11/2018 11:44:06 ssh 192.168.2.21 /usr/sbin/sshd 5005 1285
8. 30/11/2018 11:44:06 ssh 192.168.2.21 /usr/sbin/sshd 5005 1286

# aureport -ts 30/11/2018 11:00:00 -te 30/11/2018 11:45:00 -u -i

User ID Report
====================================
# date time auid term host exe event
====================================
1. 30/11/2018 11:01:01 unset cron ? /usr/sbin/crond 1266
2. 30/11/2018 11:01:01 unset cron ? /usr/sbin/crond 1267
3. 30/11/2018 11:01:01 root ? ? ? 1268
4. 30/11/2018 11:01:01 root cron ? /usr/sbin/crond 1269
5. 30/11/2018 11:01:01 root cron ? /usr/sbin/crond 1270
6. 30/11/2018 11:01:01 root cron ? /usr/sbin/crond 1271
7. 30/11/2018 11:35:39 user1 ? 192.168.2.21 /usr/sbin/sshd 1272
8. 30/11/2018 11:35:39 user1 ? 192.168.2.21 /usr/sbin/sshd 1273
9. 30/11/2018 11:35:40 user1 ? 192.168.2.21 /usr/sbin/sshd 1274
10. 30/11/2018 11:35:40 user1 ? 192.168.2.21 /usr/sbin/sshd 1275
11. 30/11/2018 11:44:03 unset ? ? /sbin/shutdown 1276
12. 30/11/2018 11:44:03 unset ? ? /sbin/shutdown 1277
13. 30/11/2018 11:44:06 unset ? ? /usr/sbin/sshd 1281
14. 30/11/2018 11:44:06 unset ? ? /usr/sbin/sshd 1282
15. 30/11/2018 11:44:06 user1 ssh 192.168.2.21 /usr/sbin/sshd 1283
16. 30/11/2018 11:44:06 user1 ssh 192.168.2.21 /usr/sbin/sshd 1284
17. 30/11/2018 11:44:06 user1 ssh 192.168.2.21 /usr/sbin/sshd 1285
18. 30/11/2018 11:44:06 user1 ssh 192.168.2.21 /usr/sbin/sshd 1286
19. 30/11/2018 11:44:06 user1 ? 192.168.2.21 /usr/sbin/sshd 1287
20. 30/11/2018 11:44:06 user1 ? 192.168.2.21 /usr/sbin/sshd 1288
21. 30/11/2018 11:44:06 user1 ssh 192.168.2.21 /usr/sbin/sshd 1289
22. 30/11/2018 11:44:06 user1 ssh 192.168.2.21 /usr/sbin/sshd 1290
23. 30/11/2018 11:44:06 user1 /dev/pts/0 ? /usr/sbin/sshd 1291
24. 30/11/2018 11:44:06 user1 /dev/pts/0 ? /usr/sbin/sshd 1292
25. 30/11/2018 11:44:06 user1 ? 192.168.2.21 /usr/sbin/sshd 1293
26. 30/11/2018 11:44:06 user1 ? 192.168.2.21 /usr/sbin/sshd 1294
27. 30/11/2018 11:44:05 unset (none) ? /sbin/iptables-multi-1.4.7 1278
28. 30/11/2018 11:44:05 unset (none) ? /sbin/iptables-multi-1.4.7 1279
29. 30/11/2018 11:44:05 unset (none) ? /sbin/iptables-multi-1.4.7 1280
30. 30/11/2018 11:44:10 unset ? ? /sbin/shutdown 1295
31. 30/11/2018 11:44:10 unset ? ? /sbin/shutdown 1296
32. 30/11/2018 11:44:10 unset ? ? /sbin/shutdown 1297
33. 30/11/2018 11:44:10 unset ? ? /sbin/shutdown 1298
34. 30/11/2018 11:44:58 unset console ? /bin/su 4
35. 30/11/2018 11:44:58 unset console ? /bin/su 5
36. 30/11/2018 11:44:58 unset console ? /bin/su 6
37. 30/11/2018 11:44:58 unset console ? /bin/su 7
38. 30/11/2018 11:44:59 unset console ? /bin/su 8
39. 30/11/2018 11:44:59 unset console ? /bin/su 9
40. 30/11/2018 11:44:59 unset console ? /bin/su 10
41. 30/11/2018 11:44:59 unset console ? /bin/su 11
42. 30/11/2018 11:44:59 unset console ? /bin/su 12
43. 30/11/2018 11:44:59 unset console ? /bin/su 13
44. 30/11/2018 11:44:59 unset console ? /bin/su 14
45. 30/11/2018 11:44:59 unset console ? /bin/su 15

Exemple de crash. J'ai ajouté '> ' devant les lignes concernées 

# last -xF reboot shutdown
reboot   system boot  4.9.0-8-amd64    Tue Dec  1 10:59:41 2020   still running
shutdown system down  4.9.0-8-amd64    Tue Dec  1 10:59:04 2020 - Tue Dec  1 10:59:41 2020  (00:00)
reboot   system boot  4.9.0-8-amd64    Tue Dec  1 09:24:25 2020 - Tue Dec  1 10:59:04 2020  (01:34)
shutdown system down  4.9.0-8-amd64    Tue Dec  1 09:23:47 2020 - Tue Dec  1 09:24:25 2020  (00:00)
reboot   system boot  4.9.0-8-amd64    Tue Dec  1 09:01:15 2020 - Tue Dec  1 09:23:47 2020  (00:22)
shutdown system down  4.9.0-8-amd64    Sat Nov 28 09:02:37 2020 - Tue Dec  1 09:01:15 2020 (2+23:58)
> reboot   system boot  4.9.0-8-amd64    Fri Nov 27 04:57:54 2020 - Sat Nov 28 09:02:37 2020 (1+04:04)
reboot   system boot  4.9.0-8-amd64    Thu Nov 26 15:56:26 2020 - Sat Nov 28 09:02:37 2020 (1+17:06)
shutdown system down  4.9.0-8-amd64    Thu Nov 26 15:49:09 2020 - Thu Nov 26 15:56:26 2020  (00:07)
> reboot   system boot  4.9.0-8-amd64    Thu Nov 26 15:47:48 2020 - Thu Nov 26 15:49:09 2020  (00:01)
reboot   system boot  4.9.0-8-amd64    Thu Nov 26 15:11:50 2020 - Thu Nov 26 15:49:09 2020  (00:37)
shutdown system down  4.9.0-8-amd64    Thu Nov 26 15:11:07 2020 - Thu Nov 26 15:11:50 2020  (00:00)
reboot   system boot  4.9.0-8-amd64    Thu Nov 26 15:03:32 2020 - Thu Nov 26 15:11:07 2020  (00:07)
shutdown system down  4.9.0-8-amd64    Thu Nov 26 15:00:07 2020 - Thu Nov 26 15:03:32 2020  (00:03)
reboot   system boot  4.9.0-8-amd64    Thu Nov 26 14:58:50 2020 - Thu Nov 26 15:00:07 2020  (00:01)
shutdown system down  4.9.0-8-amd64    Thu Nov 26 12:48:56 2020 - Thu Nov 26 14:58:50 2020  (02:09)
> reboot   system boot  4.9.0-8-amd64    Thu Nov 26 08:05:37 2020 - Thu Nov 26 12:48:56 2020  (04:43)
reboot   system boot  4.9.0-8-amd64    Wed Nov 25 14:59:50 2020 - Thu Nov 26 12:48:56 2020  (21:49)
shutdown system down  4.9.0-8-amd64    Wed Nov 25 14:57:52 2020 - Wed Nov 25 14:59:50 2020  (00:01)
reboot   system boot  4.9.0-8-amd64    Wed Nov 25 14:57:00 2020 - Wed Nov 25 14:57:52 2020  (00:00)
shutdown system down  4.9.0-8-amd64    Wed Nov 25 14:44:33 2020 - Wed Nov 25 14:57:00 2020  (00:12)
reboot   system boot  4.9.0-8-amd64    Wed Nov 25 14:43:11 2020 - Wed Nov 25 14:44:33 2020  (00:01)
shutdown system down  4.9.0-8-amd64    Wed Nov 25 14:42:33 2020 - Wed Nov 25 14:43:11 2020  (00:00)
reboot   system boot  4.9.0-8-amd64    Wed Nov 25 14:40:44 2020 - Wed Nov 25 14:42:33 2020  (00:01)
shutdown system down  4.9.0-8-amd64    Wed Nov 25 14:40:07 2020 - Wed Nov 25 14:40:44 2020  (00:00)
> reboot   system boot  4.9.0-8-amd64    Wed Nov 25 14:21:43 2020 - Wed Nov 25 14:40:07 2020  (00:18)
> reboot   system boot  4.9.0-8-amd64    Wed Nov 25 13:45:45 2020 - Wed Nov 25 14:40:07 2020  (00:54)
> reboot   system boot  4.9.0-8-amd64    Wed Nov 25 06:14:31 2020 - Wed Nov 25 14:40:07 2020  (08:25)
> reboot   system boot  4.9.0-8-amd64    Wed Nov 25 04:59:05 2020 - Wed Nov 25 14:40:07 2020  (09:41)
> reboot   system boot  4.9.0-8-amd64    Wed Nov 25 04:27:03 2020 - Wed Nov 25 14:40:07 2020  (10:13)
> reboot   system boot  4.9.0-8-amd64    Wed Nov 25 04:03:13 2020 - Wed Nov 25 14:40:07 2020  (10:36)
> reboot   system boot  4.9.0-8-amd64    Wed Nov 25 03:29:28 2020 - Wed Nov 25 14:40:07 2020  (11:10)
> reboot   system boot  4.9.0-8-amd64    Tue Nov 24 18:01:42 2020 - Wed Nov 25 14:40:07 2020  (20:38)
> reboot   system boot  4.9.0-8-amd64    Tue Nov 24 11:35:04 2020 - Wed Nov 25 14:40:07 2020 (1+03:05)
> reboot   system boot  4.9.0-8-amd64    Tue Nov 24 03:15:07 2020 - Wed Nov 25 14:40:07 2020 (1+11:25)
> reboot   system boot  4.9.0-8-amd64    Tue Nov 24 02:14:00 2020 - Wed Nov 25 14:40:07 2020 (1+12:26)
> reboot   system boot  4.9.0-8-amd64    Mon Nov 23 15:54:34 2020 - Wed Nov 25 14:40:07 2020 (1+22:45)
> reboot   system boot  4.9.0-8-amd64    Mon Nov 23 15:45:29 2020 - Wed Nov 25 14:40:07 2020 (1+22:54)
> reboot   system boot  4.9.0-8-amd64    Mon Nov 23 07:37:38 2020 - Wed Nov 25 14:40:07 2020 (2+07:02)
> reboot   system boot  4.9.0-8-amd64    Mon Nov 23 04:31:22 2020 - Wed Nov 25 14:40:07 2020 (2+10:08)
> reboot   system boot  4.9.0-8-amd64    Sat Nov 21 18:10:22 2020 - Wed Nov 25 14:40:07 2020 (3+20:29)
reboot   system boot  4.9.0-8-amd64    Thu Nov 19 18:45:32 2020 - Wed Nov 25 14:40:07 2020 (5+19:54)
shutdown system down  4.9.0-8-amd64    Thu Nov 19 18:37:38 2020 - Thu Nov 19 18:45:32 2020  (00:07)
reboot   system boot  4.9.0-8-amd64    Thu Nov 19 18:33:25 2020 - Thu Nov 19 18:37:38 2020  (00:04)
shutdown system down  4.9.0-8-amd64    Thu Nov 19 18:32:02 2020 - Thu Nov 19 18:33:25 2020  (00:01)
> reboot   system boot  4.9.0-8-amd64    Thu Nov 19 09:21:56 2020 - Thu Nov 19 18:32:02 2020  (09:10)
> reboot   system boot  4.9.0-8-amd64    Thu Nov 19 02:49:49 2020 - Thu Nov 19 18:32:02 2020  (15:42)
reboot   system boot  4.9.0-8-amd64    Tue Nov 17 09:20:40 2020 - Thu Nov 19 18:32:02 2020 (2+09:11)
shutdown system down  4.9.0-8-amd64    Tue Nov 17 09:19:57 2020 - Tue Nov 17 09:20:40 2020  (00:00)
reboot   system boot  4.9.0-8-amd64    Tue Nov 17 10:33:39 2020 - Tue Nov 17 09:19:57 2020  (-1:-13)
shutdown system down  4.9.0-8-amd64    Tue Nov 17 01:49:22 2020 - Tue Nov 17 10:33:39 2020  (08:44)
reboot   system boot  4.9.0-8-amd64    Tue Nov 17 01:47:26 2020 - Tue Nov 17 01:49:22 2020  (00:01)
shutdown system down  4.9.0-8-amd64    Tue Nov 17 01:40:34 2020 - Tue Nov 17 01:47:26 2020  (00:06)
reboot   system boot  4.9.0-8-amd64    Tue Nov 17 01:34:07 2020 - Tue Nov 17 01:40:34 2020  (00:06)
shutdown system down  4.9.0-8-amd64    Mon Nov 16 14:15:14 2020 - Tue Nov 17 01:34:07 2020  (11:18)
reboot   system boot  4.9.0-8-amd64    Mon Nov 16 13:50:51 2020 - Mon Nov 16 14:15:14 2020  (00:24)
shutdown system down  4.9.0-8-amd64    Mon Nov 16 12:04:12 2020 - Mon Nov 16 13:50:51 2020  (01:46)
reboot   system boot  4.9.0-8-amd64    Mon Nov 16 12:00:40 2020 - Mon Nov 16 12:04:12 2020  (00:03)
shutdown system down  4.9.0-8-amd64    Mon Nov 16 11:59:59 2020 - Mon Nov 16 12:00:40 2020  (00:00)
reboot   system boot  4.9.0-8-amd64    Mon Nov 16 11:44:51 2020 - Mon Nov 16 11:59:59 2020  (00:15)
shutdown system down  4.9.0-8-amd64    Mon Nov 16 11:35:48 2020 - Mon Nov 16 11:44:51 2020  (00:09)
reboot   system boot  4.9.0-8-amd64    Mon Nov 16 11:33:51 2020 - Mon Nov 16 11:35:48 2020  (00:01)
shutdown system down  4.9.0-8-amd64    Mon Nov 16 11:32:11 2020 - Mon Nov 16 11:33:51 2020  (00:01)
reboot   system boot  4.9.0-8-amd64    Mon Nov 16 11:29:10 2020 - Mon Nov 16 11:32:11 2020  (00:03)

wtmp begins Sun Nov  1 06:37:41 2020

List of unexpected shutdown. Normally “reboot” should come after “shutdown”

2025/03/24 15:06

<< Billets récents | Anciens billets >>

blog.txt · Dernière modification : de 127.0.0.1
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki