Iobroker nicht mehr erreichbar / Festplatte voll?
-
@thomas-braun said in Iobroker nicht mehr erreichbar / Festplatte voll?:
df -h
ok zu früh gefreut:
pi@raspberrypi:/opt/iobroker $ df -h Filesystem Size Used Avail Use% Mounted on /dev/root 29G 28G 0 100% / devtmpfs 1.8G 0 1.8G 0% /dev tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs 1.9G 25M 1.9G 2% /run tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup /dev/sda1 253M 49M 204M 20% /boot tmpfs 384M 0 384M 0% /run/user/1000 pi@raspberrypi:/opt/iobroker $ iob restart pi@raspberrypi:/opt/iobroker $ iob diag pi@raspberrypi:/opt/iobroker $ iob diag pi@raspberrypi:/opt/iobroker $ -
sudo tail -200 /var/log/kern.log -
@erazor86 sagte in Iobroker nicht mehr erreichbar / Festplatte voll?:
sudo lsof/var/log/kern.log
Moin,
da fehlt ein Leerzeichen!
# sudo lsof /var/log/kern.logKopieren nicht Abschreiben
VG
Bernd -
@dp20eic said in Iobroker nicht mehr erreichbar / Festplatte voll?:
sudo lsof /var/log/kern.log
ich hatte beides probiert.. kommt leider bei beidem die gleiche Meldung
pi@raspberrypi:/opt/iobroker $ sudo lsof /var/log/kern.log sudo: lsof: command not found -
@thomas-braun said in Iobroker nicht mehr erreichbar / Festplatte voll?:
sudo tail -200 /var/log/kern.log
pi@raspberrypi:/opt/iobroker $ sudo lsof /var/log/kern.log sudo: lsof: command not found pi@raspberrypi:/opt/iobroker $ sudo tail -200 /var/log/kern.log Oct 24 11:42:56 raspberrypi kernel: [ 1.207680] pci_bus 0000:00: root bus resource [bus 00-ff] Oct 24 11:42:56 raspberrypi kernel: [ 1.207715] pci_bus 0000:00: root bus resource [mem 0x600000000-0x63fffffff] (bus address [0xc0000000-0xffffffff]) Oct 24 11:42:56 raspberrypi kernel: [ 1.207828] pci 0000:00:00.0: [14e4:2711] type 01 class 0x060400 Oct 24 11:42:56 raspberrypi kernel: [ 1.208085] pci 0000:00:00.0: PME# supported from D0 D3hot Oct 24 11:42:56 raspberrypi kernel: [ 1.211577] PCI: bus0: Fast back to back transfers disabled Oct 24 11:42:56 raspberrypi kernel: [ 1.211932] pci 0000:01:00.0: [1106:3483] type 00 class 0x0c0330 Oct 24 11:42:56 raspberrypi kernel: [ 1.212076] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00000fff 64bit] Oct 24 11:42:56 raspberrypi kernel: [ 1.212527] pci 0000:01:00.0: PME# supported from D0 D3cold Oct 24 11:42:56 raspberrypi kernel: [ 1.216022] PCI: bus1: Fast back to back transfers disabled Oct 24 11:42:56 raspberrypi kernel: [ 1.216138] pci 0000:00:00.0: BAR 8: assigned [mem 0x600000000-0x6000fffff] Oct 24 11:42:56 raspberrypi kernel: [ 1.216179] pci 0000:01:00.0: BAR 0: assigned [mem 0x600000000-0x600000fff 64bit] Oct 24 11:42:56 raspberrypi kernel: [ 1.216283] pci 0000:00:00.0: PCI bridge to [bus 01] Oct 24 11:42:56 raspberrypi kernel: [ 1.216322] pci 0000:00:00.0: bridge window [mem 0x600000000-0x6000fffff] Oct 24 11:42:56 raspberrypi kernel: [ 1.216744] pcieport 0000:00:00.0: enabling device (0140 -> 0142) Oct 24 11:42:56 raspberrypi kernel: [ 1.216992] pcieport 0000:00:00.0: PME: Signaling with IRQ 62 Oct 24 11:42:56 raspberrypi kernel: [ 1.225698] iproc-rng200 fe104000.rng: hwrng registered Oct 24 11:42:56 raspberrypi kernel: [ 1.226026] vc-mem: phys_addr:0x00000000 mem_base=0x3eb00000 mem_size:0x3ff00000(1023 MiB) Oct 24 11:42:56 raspberrypi kernel: [ 1.226913] gpiomem-bcm2835 fe200000.gpiomem: Initialised: Registers at 0xfe200000 Oct 24 11:42:56 raspberrypi kernel: [ 1.239215] brd: module loaded Oct 24 11:42:56 raspberrypi kernel: [ 1.251549] loop: module loaded Oct 24 11:42:56 raspberrypi kernel: [ 1.253319] Loading iSCSI transport class v2.0-870. Oct 24 11:42:56 raspberrypi kernel: [ 1.256654] libphy: Fixed MDIO Bus: probed Oct 24 11:42:56 raspberrypi kernel: [ 1.258364] bcmgenet fd580000.ethernet: GENET 5.0 EPHY: 0x0000 Oct 24 11:42:56 raspberrypi kernel: [ 1.275207] libphy: bcmgenet MII bus: probed Oct 24 11:42:56 raspberrypi kernel: [ 1.355325] unimac-mdio unimac-mdio.-19: Broadcom UniMAC MDIO bus Oct 24 11:42:56 raspberrypi kernel: [ 1.356517] usbcore: registered new interface driver r8152 Oct 24 11:42:56 raspberrypi kernel: [ 1.356604] usbcore: registered new interface driver lan78xx Oct 24 11:42:56 raspberrypi kernel: [ 1.356697] usbcore: registered new interface driver smsc95xx Oct 24 11:42:56 raspberrypi kernel: [ 1.358350] xhci_hcd 0000:01:00.0: enabling device (0140 -> 0142) Oct 24 11:42:56 raspberrypi kernel: [ 1.358531] xhci_hcd 0000:01:00.0: xHCI Host Controller Oct 24 11:42:56 raspberrypi kernel: [ 1.358580] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1 Oct 24 11:42:56 raspberrypi kernel: [ 1.361973] xhci_hcd 0000:01:00.0: hcc params 0x002841eb hci version 0x100 quirks 0x0000060000000890 Oct 24 11:42:56 raspberrypi kernel: [ 1.363334] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10 Oct 24 11:42:56 raspberrypi kernel: [ 1.363376] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Oct 24 11:42:56 raspberrypi kernel: [ 1.363412] usb usb1: Product: xHCI Host Controller Oct 24 11:42:56 raspberrypi kernel: [ 1.363442] usb usb1: Manufacturer: Linux 5.10.63-v7l+ xhci-hcd Oct 24 11:42:56 raspberrypi kernel: [ 1.363473] usb usb1: SerialNumber: 0000:01:00.0 Oct 24 11:42:56 raspberrypi kernel: [ 1.364208] hub 1-0:1.0: USB hub found Oct 24 11:42:56 raspberrypi kernel: [ 1.364323] hub 1-0:1.0: 1 port detected Oct 24 11:42:56 raspberrypi kernel: [ 1.365005] xhci_hcd 0000:01:00.0: xHCI Host Controller Oct 24 11:42:56 raspberrypi kernel: [ 1.365048] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2 Oct 24 11:42:56 raspberrypi kernel: [ 1.365093] xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed Oct 24 11:42:56 raspberrypi kernel: [ 1.365700] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.10 Oct 24 11:42:56 raspberrypi kernel: [ 1.365740] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Oct 24 11:42:56 raspberrypi kernel: [ 1.365776] usb usb2: Product: xHCI Host Controller Oct 24 11:42:56 raspberrypi kernel: [ 1.365805] usb usb2: Manufacturer: Linux 5.10.63-v7l+ xhci-hcd Oct 24 11:42:56 raspberrypi kernel: [ 1.365836] usb usb2: SerialNumber: 0000:01:00.0 Oct 24 11:42:56 raspberrypi kernel: [ 1.366578] hub 2-0:1.0: USB hub found Oct 24 11:42:56 raspberrypi kernel: [ 1.366696] hub 2-0:1.0: 4 ports detected Oct 24 11:42:56 raspberrypi kernel: [ 1.368409] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) Oct 24 11:42:56 raspberrypi kernel: [ 1.368731] dwc_otg: FIQ enabled Oct 24 11:42:56 raspberrypi kernel: [ 1.368746] dwc_otg: NAK holdoff enabled Oct 24 11:42:56 raspberrypi kernel: [ 1.368761] dwc_otg: FIQ split-transaction FSM enabled Oct 24 11:42:56 raspberrypi kernel: [ 1.368778] Module dwc_common_port init Oct 24 11:42:56 raspberrypi kernel: [ 1.369242] usbcore: registered new interface driver uas Oct 24 11:42:56 raspberrypi kernel: [ 1.369379] usbcore: registered new interface driver usb-storage Oct 24 11:42:56 raspberrypi kernel: [ 1.369591] mousedev: PS/2 mouse device common for all mice Oct 24 11:42:56 raspberrypi kernel: [ 1.371242] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer Oct 24 11:42:56 raspberrypi kernel: [ 1.374643] sdhci: Secure Digital Host Controller Interface driver Oct 24 11:42:56 raspberrypi kernel: [ 1.374677] sdhci: Copyright(c) Pierre Ossman Oct 24 11:42:56 raspberrypi kernel: [ 1.375484] mmc-bcm2835 fe300000.mmcnr: could not get clk, deferring probe Oct 24 11:42:56 raspberrypi kernel: [ 1.376078] sdhci-pltfm: SDHCI platform and OF driver helper Oct 24 11:42:56 raspberrypi kernel: [ 1.380224] ledtrig-cpu: registered to indicate activity on CPUs Oct 24 11:42:56 raspberrypi kernel: [ 1.380573] hid: raw HID events driver (C) Jiri Kosina Oct 24 11:42:56 raspberrypi kernel: [ 1.380808] usbcore: registered new interface driver usbhid Oct 24 11:42:56 raspberrypi kernel: [ 1.380839] usbhid: USB HID core driver Oct 24 11:42:56 raspberrypi kernel: [ 1.386881] Initializing XFRM netlink socket Oct 24 11:42:56 raspberrypi kernel: [ 1.386944] NET: Registered protocol family 17 Oct 24 11:42:56 raspberrypi kernel: [ 1.387087] Key type dns_resolver registered Oct 24 11:42:56 raspberrypi kernel: [ 1.387431] Registering SWP/SWPB emulation handler Oct 24 11:42:56 raspberrypi kernel: [ 1.387614] registered taskstats version 1 Oct 24 11:42:56 raspberrypi kernel: [ 1.387655] Loading compiled-in X.509 certificates Oct 24 11:42:56 raspberrypi kernel: [ 1.388527] Key type ._fscrypt registered Oct 24 11:42:56 raspberrypi kernel: [ 1.388557] Key type .fscrypt registered Oct 24 11:42:56 raspberrypi kernel: [ 1.388585] Key type fscrypt-provisioning registered Oct 24 11:42:56 raspberrypi kernel: [ 1.400115] uart-pl011 fe201000.serial: there is not valid maps for state default Oct 24 11:42:56 raspberrypi kernel: [ 1.400447] uart-pl011 fe201000.serial: cts_event_workaround enabled Oct 24 11:42:56 raspberrypi kernel: [ 1.400538] fe201000.serial: ttyAMA0 at MMIO 0xfe201000 (irq = 36, base_baud = 0) is a PL011 rev2 Oct 24 11:42:56 raspberrypi kernel: [ 1.408608] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver Oct 24 11:42:56 raspberrypi kernel: [ 1.409715] mmc-bcm2835 fe300000.mmcnr: mmc_debug:0 mmc_debug2:0 Oct 24 11:42:56 raspberrypi kernel: [ 1.409749] mmc-bcm2835 fe300000.mmcnr: DMA channel allocated Oct 24 11:42:56 raspberrypi kernel: [ 1.440004] of_cfs_init Oct 24 11:42:56 raspberrypi kernel: [ 1.440281] of_cfs_init: OK Oct 24 11:42:56 raspberrypi kernel: [ 1.447588] mmc1: Controller never released inhibit bit(s). Oct 24 11:42:56 raspberrypi kernel: [ 1.471253] mmc1: queuing unknown CIS tuple 0x80 (2 bytes) Oct 24 11:42:56 raspberrypi kernel: [ 1.472965] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) Oct 24 11:42:56 raspberrypi kernel: [ 1.474672] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) Oct 24 11:42:56 raspberrypi kernel: [ 1.478089] mmc1: queuing unknown CIS tuple 0x80 (7 bytes) Oct 24 11:42:56 raspberrypi kernel: [ 1.479795] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) Oct 24 11:42:56 raspberrypi kernel: [ 1.485253] mmc0: SDHCI controller on fe340000.mmc [fe340000.mmc] using ADMA Oct 24 11:42:56 raspberrypi kernel: [ 1.485904] Waiting for root device PARTUUID=7a2feeee-02... Oct 24 11:42:56 raspberrypi kernel: [ 1.545642] usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd Oct 24 11:42:56 raspberrypi kernel: [ 1.548722] mmc1: new high speed SDIO card at address 0001 Oct 24 11:42:56 raspberrypi kernel: [ 1.577032] usb 2-1: New USB device found, idVendor=14b0, idProduct=0206, bcdDevice= 1.00 Oct 24 11:42:56 raspberrypi kernel: [ 1.577074] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1 Oct 24 11:42:56 raspberrypi kernel: [ 1.577108] usb 2-1: Product: Force LS SSD Oct 24 11:42:56 raspberrypi kernel: [ 1.577137] usb 2-1: Manufacturer: Corsair Oct 24 11:42:56 raspberrypi kernel: [ 1.577166] usb 2-1: SerialNumber: 1234567815F4 Oct 24 11:42:56 raspberrypi kernel: [ 1.603092] scsi host0: uas Oct 24 11:42:56 raspberrypi kernel: [ 1.604627] scsi 0:0:0:0: Direct-Access Corsair Force LS SSD 0 PQ: 0 ANSI: 6 Oct 24 11:42:56 raspberrypi kernel: [ 1.606824] sd 0:0:0:0: [sda] 117231408 512-byte logical blocks: (60.0 GB/55.9 GiB) Oct 24 11:42:56 raspberrypi kernel: [ 1.607041] sd 0:0:0:0: [sda] Write Protect is off Oct 24 11:42:56 raspberrypi kernel: [ 1.607077] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00 Oct 24 11:42:56 raspberrypi kernel: [ 1.607426] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 24 11:42:56 raspberrypi kernel: [ 1.608240] sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes Oct 24 11:42:56 raspberrypi kernel: [ 1.611321] sda: sda1 sda2 Oct 24 11:42:56 raspberrypi kernel: [ 1.614496] sd 0:0:0:0: [sda] Attached SCSI disk Oct 24 11:42:56 raspberrypi kernel: [ 1.652086] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) Oct 24 11:42:56 raspberrypi kernel: [ 1.652185] VFS: Mounted root (ext4 filesystem) readonly on device 8:2. Oct 24 11:42:56 raspberrypi kernel: [ 1.654243] devtmpfs: mounted Oct 24 11:42:56 raspberrypi kernel: [ 1.664143] Freeing unused kernel memory: 2048K Oct 24 11:42:56 raspberrypi kernel: [ 1.705486] Run /sbin/init as init process Oct 24 11:42:56 raspberrypi kernel: [ 1.705516] with arguments: Oct 24 11:42:56 raspberrypi kernel: [ 1.705531] /sbin/init Oct 24 11:42:56 raspberrypi kernel: [ 1.705545] with environment: Oct 24 11:42:56 raspberrypi kernel: [ 1.705560] HOME=/ Oct 24 11:42:56 raspberrypi kernel: [ 1.705574] TERM=linux Oct 24 11:42:56 raspberrypi kernel: [ 1.725615] usb 1-1: new high-speed USB device number 2 using xhci_hcd Oct 24 11:42:56 raspberrypi kernel: [ 1.907733] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.21 Oct 24 11:42:56 raspberrypi kernel: [ 1.907779] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 Oct 24 11:42:56 raspberrypi kernel: [ 1.907813] usb 1-1: Product: USB2.0 Hub Oct 24 11:42:56 raspberrypi kernel: [ 1.909890] hub 1-1:1.0: USB hub found Oct 24 11:42:56 raspberrypi kernel: [ 1.910131] hub 1-1:1.0: 4 ports detected Oct 24 11:42:56 raspberrypi kernel: [ 1.967238] NET: Registered protocol family 10 Oct 24 11:42:56 raspberrypi kernel: [ 1.968685] Segment Routing with IPv6 Oct 24 11:42:56 raspberrypi kernel: [ 2.607403] random: systemd: uninitialized urandom read (16 bytes read) Oct 24 11:42:56 raspberrypi kernel: [ 2.615594] random: systemd: uninitialized urandom read (16 bytes read) Oct 24 11:42:56 raspberrypi kernel: [ 2.619523] random: systemd: uninitialized urandom read (16 bytes read) Oct 24 11:42:56 raspberrypi kernel: [ 3.118773] EXT4-fs (sda2): re-mounted. Opts: (null) Oct 24 11:42:56 raspberrypi kernel: [ 3.795339] rpivid-mem feb00000.hevc-decoder: rpivid-hevcmem initialised: Registers at 0xfeb00000 length 0x00010000 Oct 24 11:42:56 raspberrypi kernel: [ 3.795967] rpivid-mem feb10000.rpivid-local-intc: rpivid-intcmem initialised: Registers at 0xfeb10000 length 0x00001000 Oct 24 11:42:56 raspberrypi kernel: [ 3.796534] rpivid-mem feb20000.h264-decoder: rpivid-h264mem initialised: Registers at 0xfeb20000 length 0x00010000 Oct 24 11:42:56 raspberrypi kernel: [ 3.797073] rpivid-mem feb30000.vp9-decoder: rpivid-vp9mem initialised: Registers at 0xfeb30000 length 0x00010000 Oct 24 11:42:56 raspberrypi kernel: [ 3.884618] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned. Oct 24 11:42:56 raspberrypi kernel: [ 3.888199] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned. Oct 24 11:42:56 raspberrypi kernel: [ 3.889781] mc: Linux media interface: v0.10 Oct 24 11:42:56 raspberrypi kernel: [ 3.903059] bcm2835_vc_sm_cma_probe: Videocore shared memory driver Oct 24 11:42:56 raspberrypi kernel: [ 3.903084] [vc_sm_connected_init]: start Oct 24 11:42:56 raspberrypi kernel: [ 3.922455] [vc_sm_connected_init]: installed successfully Oct 24 11:42:56 raspberrypi kernel: [ 3.928161] bcm2835_audio bcm2835_audio: card created with 8 channels Oct 24 11:42:56 raspberrypi kernel: [ 3.946690] videodev: Linux video capture interface: v2.00 Oct 24 11:42:56 raspberrypi kernel: [ 3.962512] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned. Oct 24 11:42:56 raspberrypi kernel: [ 3.963869] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned. Oct 24 11:42:56 raspberrypi kernel: [ 3.982102] bcm2835_isp: module is from the staging directory, the quality is unknown, you have been warned. Oct 24 11:42:56 raspberrypi kernel: [ 4.004861] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned. Oct 24 11:42:56 raspberrypi kernel: [ 4.012310] bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video13 Oct 24 11:42:56 raspberrypi kernel: [ 4.012850] bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video14 Oct 24 11:42:56 raspberrypi kernel: [ 4.013555] bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video15 Oct 24 11:42:56 raspberrypi kernel: [ 4.013864] bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video16 Oct 24 11:42:56 raspberrypi kernel: [ 4.013897] bcm2835-isp bcm2835-isp: Register output node 0 with media controller Oct 24 11:42:56 raspberrypi kernel: [ 4.013923] bcm2835-isp bcm2835-isp: Register capture node 1 with media controller Oct 24 11:42:56 raspberrypi kernel: [ 4.013946] bcm2835-isp bcm2835-isp: Register capture node 2 with media controller Oct 24 11:42:56 raspberrypi kernel: [ 4.013968] bcm2835-isp bcm2835-isp: Register capture node 3 with media controller Oct 24 11:42:56 raspberrypi kernel: [ 4.014163] bcm2835-isp bcm2835-isp: Loaded V4L2 bcm2835-isp Oct 24 11:42:56 raspberrypi kernel: [ 4.035473] cfg80211: Loading compiled-in X.509 certificates for regulatory database Oct 24 11:42:56 raspberrypi kernel: [ 4.084263] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned. Oct 24 11:42:56 raspberrypi kernel: [ 4.125844] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Oct 24 11:42:56 raspberrypi kernel: [ 4.131060] bcm2835-codec bcm2835-codec: Device registered as /dev/video10 Oct 24 11:42:56 raspberrypi kernel: [ 4.131124] bcm2835-codec bcm2835-codec: Loaded V4L2 decode Oct 24 11:42:56 raspberrypi kernel: [ 4.152115] bcm2835-codec bcm2835-codec: Device registered as /dev/video11 Oct 24 11:42:56 raspberrypi kernel: [ 4.152161] bcm2835-codec bcm2835-codec: Loaded V4L2 encode Oct 24 11:42:56 raspberrypi kernel: [ 4.187406] bcm2835-codec bcm2835-codec: Device registered as /dev/video12 Oct 24 11:42:56 raspberrypi kernel: [ 4.187524] bcm2835-codec bcm2835-codec: Loaded V4L2 isp Oct 24 11:42:56 raspberrypi kernel: [ 4.197382] brcmfmac: F1 signature read @0x18000000=0x15264345 Oct 24 11:42:56 raspberrypi kernel: [ 4.199442] bcm2835-codec bcm2835-codec: Device registered as /dev/video18 Oct 24 11:42:56 raspberrypi kernel: [ 4.199505] bcm2835-codec bcm2835-codec: Loaded V4L2 image_fx Oct 24 11:42:56 raspberrypi kernel: [ 4.215428] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 Oct 24 11:42:56 raspberrypi kernel: [ 4.217461] usbcore: registered new interface driver brcmfmac Oct 24 11:42:56 raspberrypi kernel: [ 4.267380] [drm] Initialized v3d 1.0.0 20180419 for fec00000.v3d on minor 0 Oct 24 11:42:56 raspberrypi kernel: [ 4.273451] sd 0:0:0:0: Attached scsi generic sg0 type 0 Oct 24 11:42:56 raspberrypi kernel: [ 4.352522] [drm] No displays found. Consider forcing hotplug if HDMI is attached Oct 24 11:42:56 raspberrypi kernel: [ 4.352670] vc4-drm gpu: bound fe600000.firmwarekms (ops vc4_fkms_ops [vc4]) Oct 24 11:42:56 raspberrypi kernel: [ 4.360451] [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 1 Oct 24 11:42:56 raspberrypi kernel: [ 4.478969] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 Oct 24 11:42:56 raspberrypi kernel: [ 4.479088] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 Oct 24 11:42:56 raspberrypi kernel: [ 4.488535] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Jan 4 2021 19:56:29 version 7.45.229 (617f1f5 CY) FWID 01-2dbd9d2e Oct 24 11:42:56 raspberrypi kernel: [ 6.570331] random: crng init done Oct 24 11:42:56 raspberrypi kernel: [ 6.570362] random: 7 urandom warning(s) missed due to ratelimiting Oct 24 11:42:56 raspberrypi kernel: [ 6.676105] 8021q: 802.1Q VLAN Support v1.8 Oct 24 11:42:56 raspberrypi kernel: [ 6.729120] uart-pl011 fe201000.serial: no DMA platform data Oct 24 11:42:57 raspberrypi kernel: [ 6.926777] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled Oct 24 11:42:57 raspberrypi kernel: [ 7.035965] Adding 51196k swap on /var/swap. Priority:-2 extents:133 across:23083960k SSFS Oct 24 11:42:57 raspberrypi kernel: [ 7.101788] bcmgenet fd580000.ethernet: configuring instance for external RGMII (RX delay) Oct 24 11:42:57 raspberrypi kernel: [ 7.102036] bcmgenet fd580000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off Oct 24 11:42:57 raspberrypi kernel: [ 7.102161] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Oct 24 11:42:59 raspberrypi kernel: [ 9.118481] ICMPv6: process `dhcpcd' is using deprecated sysctl (syscall) net.ipv6.neigh.eth0.retrans_time - use net.ipv6.neigh.eth0.retrans_time_ms instead Oct 24 11:43:03 raspberrypi kernel: [ 13.455693] Bluetooth: Core ver 2.22 Oct 24 11:43:03 raspberrypi kernel: [ 13.455755] NET: Registered protocol family 31 Oct 24 11:43:03 raspberrypi kernel: [ 13.455762] Bluetooth: HCI device and connection manager initialized Oct 24 11:43:03 raspberrypi kernel: [ 13.455777] Bluetooth: HCI socket layer initialized Oct 24 11:43:03 raspberrypi kernel: [ 13.455787] Bluetooth: L2CAP socket layer initialized Oct 24 11:43:03 raspberrypi kernel: [ 13.455802] Bluetooth: SCO socket layer initialized Oct 24 11:43:03 raspberrypi kernel: [ 13.464513] Bluetooth: HCI UART driver ver 2.3 Oct 24 11:43:03 raspberrypi kernel: [ 13.464524] Bluetooth: HCI UART protocol H4 registered Oct 24 11:43:03 raspberrypi kernel: [ 13.464579] Bluetooth: HCI UART protocol Three-wire (H5) registered Oct 24 11:43:03 raspberrypi kernel: [ 13.464740] Bluetooth: HCI UART protocol Broadcom registered Oct 24 11:43:03 raspberrypi kernel: [ 13.631498] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Oct 24 11:43:03 raspberrypi kernel: [ 13.631508] Bluetooth: BNEP filters: protocol multicast Oct 24 11:43:03 raspberrypi kernel: [ 13.631521] Bluetooth: BNEP socket layer initialized Oct 24 11:43:22 raspberrypi kernel: [ 31.835180] vcc-sd: disabling -
@erazor86 sagte in Iobroker nicht mehr erreichbar / Festplatte voll?:
sudo: lsof: command not found
Moin,
Linux Grundkurs, diese Meldung sagt, dass das Programm
lsofnicht gefunden wird, also ist es nicht installiert, Du kannst das nachinstallieren# sudo apt install lsofVG
Bernd -
@dp20eic said in Iobroker nicht mehr erreichbar / Festplatte voll?:
@erazor86 sagte in Iobroker nicht mehr erreichbar / Festplatte voll?:
sudo: lsof: command not found
Moin,
Linux Grundkurs, diese Meldung sagt, dass das Programm
lsofnicht gefunden wird, also ist es nicht installiert, Du kannst das nachinstallieren# sudo apt install lsofVG
Bernddanke für die Hilfe, aber leider sagt er mir, dass nicht genug freier Speicher zum installieren vorhanden ist...
pi@raspberrypi:~ $ sudo apt install lsof Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: lsof 0 upgraded, 1 newly installed, 0 to remove and 122 not upgraded. Need to get 307 kB of archives. After this operation, 447 kB of additional disk space will be used. E: You don't have enough free space in /var/cache/apt/archives/.edit: So ich habe jetzt die Partition erweitert auf volle Festplattenkapazität und iob läuft zum glück auch wieder. Jetzt gilt es nur die Ursache ausfindig zu machen und das System zu bereinigen eh mir der Speicher wieder voll läuft...
aktuell sieht es so aus:pi@raspberrypi:~ $ df -h Filesystem Size Used Avail Use% Mounted on /dev/root 55G 28G 25G 54% / devtmpfs 1.8G 0 1.8G 0% /dev tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs 1.9G 8.5M 1.9G 1% /run tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup /dev/sda1 253M 49M 204M 20% /boot tmpfs 384M 0 384M 0% /run/user/1000 pi@raspberrypi:~ $ iobroker startpi@raspberrypi:~ $ sudo apt install lsof Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: lsof 0 upgraded, 1 newly installed, 0 to remove and 122 not upgraded. Need to get 307 kB of archives. After this operation, 447 kB of additional disk space will be used. Get:1 http://mirror1.hs-esslingen.de/pub/Mirrors/archive.raspbian.org/raspbian buster/main armhf lsof armhf 4.91+dfsg-1 [307 kB] Fetched 307 kB in 0s (843 kB/s) Selecting previously unselected package lsof. (Reading database ... 50941 files and directories currently installed.) Preparing to unpack .../lsof_4.91+dfsg-1_armhf.deb ... Unpacking lsof (4.91+dfsg-1) ... Setting up lsof (4.91+dfsg-1) ... Processing triggers for man-db (2.8.5-2) ... -
Dann schau 'live' in kern.log oder syslog rein und schau was da reinläuft. Irgendwo müssen die 11GB pro file a herkommen.
tail /var/log/syslog -
Davon abgesehen würde ich dringend zu einem Umzug auf das andere System raten.
Mach ein Backup vom jetzt wieder laufenden ioBroker und pack die Umzugskartons.
-
@thomas-braun said in Iobroker nicht mehr erreichbar / Festplatte voll?:
tail /var/log/syslog
Oct 24 16:43:30 raspberrypi bash[625]: ================================== > LOG REDIRECT system.adapter.jarvis.0 => true [system.adapter.jarvis.0.logging] Oct 24 16:43:43 raspberrypi bash[625]: ================================== > LOG REDIRECT system.adapter.jarvis.1 => true [system.adapter.jarvis.1.logging] Oct 24 16:50:54 raspberrypi dhcpcd[623]: eth0: Router Advertisement from fe80::c ece:1eff:fe79:6d19 Oct 24 16:54:38 raspberrypi dhcpcd[623]: eth0: Router Advertisement from fe80::c ece:1eff:fe79:6d19 Oct 24 16:57:14 raspberrypi systemd[1]: Starting Cleanup of Temporary Directorie s... Oct 24 16:57:14 raspberrypi systemd[1]: systemd-tmpfiles-clean.service: Succeede d. Oct 24 16:57:14 raspberrypi systemd[1]: Started Cleanup of Temporary Directories . Oct 24 16:57:24 raspberrypi dhcpcd[623]: eth0: Router Advertisement from fe80::c ece:1eff:fe79:6d19 Oct 24 16:57:25 raspberrypi dhcpcd[623]: eth0: Router Advertisement from fe80::c ece:1eff:fe79:6d19 Oct 24 17:00:13 raspberrypi systemd[1]: Started Session 3 of user pi.scheint wohl was mit Jarvis zu sein...
-
@erazor86 sagte in Iobroker nicht mehr erreichbar / Festplatte voll?:
scheint wohl was mit Jarvis zu sein...
Das kannst du aus dem dutzend Zeilen nicht ableiten.
-
@erazor86 sagte in Iobroker nicht mehr erreichbar / Festplatte voll?:
Jetzt gilt es nur die Ursache ausfindig zu machen und das System zu bereinigen eh mir der Speicher wieder voll läuft
Moin,
na, wenn Du
lsofjetzt installiert hast, dann kannst Du ja mal schauen# sudo lsof /var/log/kern.log ***Dann den/die Dinste stoppen, die das File nutzen** # sudo systemctl status .... # sudo systemctl stop .... # sudo lsof /var/log/kern.log # sudo > /dev/log/kern.log # sudo systemctl start .... # sudo ls -la /var/log/kern.log*Dann auch das gleiche, mit
/var/log/syslog
Bei Dir ist das Logfile Rotation nicht aktiv, oder kaputt, deswegen wachsen die Logs an, normalerweise, wird entweder täglich, oder nach Größe rotiert.VG
BerndP.S.: Danke @Thomas-Braun, habe
(in/ich korrigiert. -
@dp20eic sagte in Iobroker nicht mehr erreichbar / Festplatte voll?:
/var(log/kern.log
Das sollte eher jeweils
/var/log/kern.loglauten.
-
@dp20eic said in Iobroker nicht mehr erreichbar / Festplatte voll?:
sudo ls -la /var/log/kern.log*
ich habe die Befehle mal nacheinander gestartet, aber da scheint es noch irgendwo zu hängen
pi@raspberrypi:~ $ sudo lsof /var/log/kern.log pi@raspberrypi:~ $ sudo systemctl status ● raspberrypi State: degraded Jobs: 0 queued Failed: 1 units Since: Thu 1970-01-01 01:00:01 CET; 53 years 9 months ago CGroup: / ├─user.slice │ └─user-1000.slice │ ├─session-3.scope │ │ ├─3038 sshd: pi [priv] │ │ ├─3090 sshd: pi@pts/1 │ │ ├─3091 -bash │ │ ├─4139 sudo systemctl status │ │ ├─4140 systemctl status │ │ └─4141 pager │ ├─user@1000.service │ │ └─init.scope │ │ ├─748 /lib/systemd/systemd --user │ │ └─749 (sd-pam) │ └─session-1.scope │ ├─678 sshd: pi [priv] │ ├─762 sshd: pi@pts/0 │ └─763 -bash lines 1-23...skipping... ● raspberrypi State: degraded Jobs: 0 queued Failed: 1 units Since: Thu 1970-01-01 01:00:01 CET; 53 years 9 months ago CGroup: / ├─user.slice │ └─user-1000.slice │ ├─session-3.scope │ │ ├─3038 sshd: pi [priv] │ │ ├─3090 sshd: pi@pts/1 │ │ ├─3091 -bash │ │ ├─4139 sudo systemctl status │ │ ├─4140 systemctl status │ │ └─4141 pager │ ├─user@1000.service │ │ └─init.scope │ │ ├─748 /lib/systemd/systemd --user │ │ └─749 (sd-pam) │ └─session-1.scope │ ├─678 sshd: pi [priv] │ ├─762 sshd: pi@pts/0 │ └─763 -bash ├─init.scope │ └─1 /sbin/init └─system.slice ├─alsa-state.service │ └─361 /usr/sbin/alsactl -E HOME=/run/alsa -s -n 19 -c rdaemon ├─systemd-timesyncd.service │ └─311 /lib/systemd/systemd-timesyncd ├─dbus.service │ └─349 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only ├─hciuart.service │ └─643 /usr/bin/hciattach /dev/serial1 bcm43xx 3000000 flow - ├─ssh.service │ └─631 /usr/sbin/sshd -D ├─avahi-daemon.service │ ├─358 avahi-daemon: running [raspberrypi.local] │ └─373 avahi-daemon: chroot helper ├─system-getty.slice │ └─getty@tty1.service │ └─630 /sbin/agetty -o -p -- \u --noclear tty1 linux ├─wpa_supplicant.service │ └─372 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant ├─triggerhappy.service │ └─376 /usr/sbin/thd --triggers /etc/triggerhappy/triggers.d/ --socket /run/thd.socket --user nobody --deviceglob /dev/input/event* ├─systemd-logind.service │ └─389 /lib/systemd/systemd-logind ├─cron.service │ └─356 /usr/sbin/cron -f ├─systemd-udevd.service │ └─152 /lib/systemd/systemd-udevd ├─rsyslog.service │ └─4039 /usr/sbin/rsyslogd -n -iNONE ├─bluetooth.service │ └─658 /usr/lib/bluetooth/bluetoothd ├─systemd-journald.service │ └─134 /lib/systemd/systemd-journald ├─rng-tools.service │ └─351 /usr/sbin/rngd -r /dev/hwrng └─dhcpcd.service ├─486 wpa_supplicant -B -c/etc/wpa_supplicant/wpa_supplicant.conf -iwlan0 -Dnl80211,wext lines 1-62 ● raspberrypi State: degraded Jobs: 0 queued Failed: 1 units Since: Thu 1970-01-01 01:00:01 CET; 53 years 9 months ago CGroup: / ├─user.slice │ └─user-1000.slice │ ├─session-3.scope │ │ ├─3038 sshd: pi [priv] │ │ ├─3090 sshd: pi@pts/1 │ │ ├─3091 -bash │ │ ├─4139 sudo systemctl status │ │ ├─4140 systemctl status │ │ └─4141 pager │ ├─user@1000.service │ │ └─init.scope │ │ ├─748 /lib/systemd/systemd --user │ │ └─749 (sd-pam) │ └─session-1.scope │ ├─678 sshd: pi [priv] │ ├─762 sshd: pi@pts/0 │ └─763 -bash ├─init.scope │ └─1 /sbin/init └─system.slice ├─alsa-state.service │ └─361 /usr/sbin/alsactl -E HOME=/run/alsa -s -n 19 -c rdaemon ├─systemd-timesyncd.service │ └─311 /lib/systemd/systemd-timesyncd ├─dbus.service │ └─349 /usr/bin/dbus-daemon --system --address=systemd: --nofork - ├─hciuart.service │ └─643 /usr/bin/hciattach /dev/serial1 bcm43xx 3000000 flow - ├─ssh.service │ └─631 /usr/sbin/sshd -D ├─avahi-daemon.service │ ├─358 avahi-daemon: running [raspberrypi.local] │ └─373 avahi-daemon: chroot helper ├─system-getty.slice │ └─getty@tty1.service │ └─630 /sbin/agetty -o -p -- \u --noclear tty1 linux ├─wpa_supplicant.service │ └─372 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant ├─triggerhappy.service │ └─376 /usr/sbin/thd --triggers /etc/triggerhappy/triggers.d/ --so ├─systemd-logind.service │ └─389 /lib/systemd/systemd-logind ├─cron.service │ └─356 /usr/sbin/cron -f ├─systemd-udevd.service │ └─152 /lib/systemd/systemd-udevd ├─rsyslog.service │ └─4039 /usr/sbin/rsyslogd -n -iNONE ├─bluetooth.service │ └─658 /usr/lib/bluetooth/bluetoothd ├─systemd-journald.service │ └─134 /lib/systemd/systemd-journald ├─rng-tools.service │ └─351 /usr/sbin/rngd -r /dev/hwrng └─dhcpcd.service ├─486 wpa_supplicant -B -c/etc/wpa_supplicant/wpa_supplicant.conf └─623 /sbin/dhcpcd -q -w pi@raspberrypi:~ $ sudo systemctl stop Too few arguments. pi@raspberrypi:~ $ sudo lsof /var/log/kern.log pi@raspberrypi:~ $ sudo > /dev/log/kern.log -bash: /dev/log/kern.log: Not a directory pi@raspberrypi:~ $ sudo > /dev/log/kern.log -bash: /dev/log/kern.log: Not a directory pi@raspberrypi:~ $ sudo systemctl start Too few arguments. pi@raspberrypi:~ $ sudo ls -la /var/log/kern.log* -rw-r----- 1 root adm 12281625684 Oct 24 16:41 /var/log/kern.log -rw-r----- 1 root adm 456 Sep 23 20:36 /var/log/kern.log.1 -rw-r----- 1 root adm 298 Sep 18 17:02 /var/log/kern.log.2.gz -rw-r----- 1 root adm 24217 Sep 5 09:56 /var/log/kern.log.3.gz -rw-r----- 1 root adm 189 Aug 27 21:59 /var/log/kern.log.4.gz -
echo "" | sudo tee /var/log/kern.logsollte das kern.log löschen. Analog
echo "" | sudo tee /var/log/syslog -
@thomas-braun said in Iobroker nicht mehr erreichbar / Festplatte voll?:
echo "" | sudo tee /var/log/kern.logsollte das kern.log löschen. Analog
echo "" | sudo tee /var/log/syslogsuper! danke euch beiden
pi@raspberrypi:~ $ df -h Filesystem Size Used Avail Use% Mounted on /dev/root 55G 5.1G 48G 10% / devtmpfs 1.8G 0 1.8G 0% /dev tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs 1.9G 17M 1.9G 1% /run tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup /dev/sda1 253M 49M 204M 20% /boot tmpfs 384M 0 384M 0% /run/user/1000jetzt habe ich erstmal was Zeit gewonnen und kann mal was essen
-
@erazor86 sagte in Iobroker nicht mehr erreichbar / Festplatte voll?:
sudo systemctl status
Moin,
nach dem
statusmuss natürlich auch das eingetragen werden, was beilsofangezeigt wird.
Bei mir z. B.promtail, ist nur ein Dienst bei mir# lsof /var/log/kern.log COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME rsyslogd 1503 root 12w REG 253,1 33738 50334529 /var/log/kern.log promtail 2879 promtail 25r REG 253,1 33738 50334529 /var/log/kern.logWenn bei dir da nichts kommt, dann muss man auch nichts stoppen, und kann gleich zum Löschen übergehen, die Methode von @Thomas-Braun geht auch, solange da keiner einen
Filehandledrauf hat, mitunter, zieht man damit einem Programm den Stuhl unter dem Arsch weg, führt aber hier und jetzt zuweit.
Gut, dass es jetzt erst einmal wieder aufgeräumt aussieht.
Du solltest aber schauen, ob Log Rotate läuftdp20eic@iobroker:~$ systemctl status logrotate.timer * logrotate.timer - Daily rotation of log files Loaded: loaded (/lib/systemd/system/logrotate.timer; enabled; vendor preset: enabled) Active: active (waiting) since Tue 2023-10-17 09:21:40 CEST; 1 weeks 0 days ago Trigger: Wed 2023-10-25 00:00:00 CEST; 5h 17min left Triggers: * logrotate.service Docs: man:logrotate(8) man:logrotate.conf(5) dp20eic@iobroker:~$ systemctl status logrotate.service * logrotate.service - Rotate log files Loaded: loaded (/lib/systemd/system/logrotate.service; static) Active: inactive (dead) since Tue 2023-10-24 00:00:43 CEST; 18h ago TriggeredBy: * logrotate.timer Docs: man:logrotate(8) man:logrotate.conf(5) Process: 89270 ExecStart=/usr/sbin/logrotate /etc/logrotate.conf (code=exited, status=0/SUCCESS) Main PID: 89270 (code=exited, status=0/SUCCESS) CPU: 55msWie rotiert wird, steht in den Files unter
/etc/logrotate.dz.b. so sieht das bei meinemDebian - Bookwormausdp20eic@iobroker:~$ ls -la /etc/logrotate.d/* -rw-r--r-- 1 root root 120 Apr 19 2019 /etc/logrotate.d/alternatives -rw-r--r-- 1 root root 173 May 12 2020 /etc/logrotate.d/apt -rw-r--r-- 1 root root 130 Aug 29 2018 /etc/logrotate.d/btmp -rw-r--r-- 1 root root 181 Nov 28 2020 /etc/logrotate.d/cups-daemon -rw-r--r-- 1 root root 112 Apr 19 2019 /etc/logrotate.d/dpkg -rw-r--r-- 1 root root 374 Feb 17 2021 /etc/logrotate.d/rsyslog -rw-r--r-- 1 root root 131 Jul 29 2021 /etc/logrotate.d/telegraf -rw-r--r-- 1 root root 145 Feb 19 2018 /etc/logrotate.d/wtmpWenn da auch wieder nichts kommt, dann setz die Kiste wirklich neu auf, denn dann laborierst du an einem toten Pferd.
VG
Bernd -
@dp20eic
kaum zu glauben, zwischen meinem letzten und diesen Post wurde mein zweiter Sohn geboren. Bin gerade ausm Kreissaal zurück, damit hätte ich heute auch nicht mehr gerechnet
nun aber zurück zum Thema
es sieht so aus, als würde soweit alles laufen...Last login: Tue Oct 24 17:00:14 2023 from 192.168.178.117 pi@raspberrypi:~ $ df -h Filesystem Size Used Avail Use% Mounted on /dev/root 55G 5.1G 48G 10% / devtmpfs 1.8G 0 1.8G 0% /dev tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs 1.9G 17M 1.9G 1% /run tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup /dev/sda1 253M 49M 204M 20% /boot tmpfs 384M 0 384M 0% /run/user/1000 pi@raspberrypi:~ $ lsof /var/log/kern.log pi@raspberrypi:~ $ systemctl status logrotate.timer ● logrotate.timer - Daily rotation of log files Loaded: loaded (/lib/systemd/system/logrotate.timer; enabled; vendor preset: Active: active (waiting) since Tue 2023-10-24 16:41:25 CEST; 7h ago Trigger: Thu 2023-10-26 00:00:00 CEST; 23h left Docs: man:logrotate(8) man:logrotate.conf(5) Oct 24 16:41:25 raspberrypi systemd[1]: Started Daily rotation of log files. ...skipping... ● logrotate.timer - Daily rotation of log files Loaded: loaded (/lib/systemd/system/logrotate.timer; enabled; vendor preset: Active: active (waiting) since Tue 2023-10-24 16:41:25 CEST; 7h ago Trigger: Thu 2023-10-26 00:00:00 CEST; 23h left Docs: man:logrotate(8) man:logrotate.conf(5) Oct 24 16:41:25 raspberrypi systemd[1]: Started Daily rotation of log files. pi@raspberrypi:~ $ systemctl status logrotate.service ● logrotate.service - Rotate log files Loaded: loaded (/lib/systemd/system/logrotate.service; static; vendor preset: Active: inactive (dead) since Wed 2023-10-25 00:00:15 CEST; 37min ago Docs: man:logrotate(8) man:logrotate.conf(5) Process: 29578 ExecStart=/usr/sbin/logrotate /etc/logrotate.conf (code=exited, Main PID: 29578 (code=exited, status=0/SUCCESS) Oct 25 00:00:14 raspberrypi systemd[1]: Starting Rotate log files... Oct 25 00:00:15 raspberrypi systemd[1]: logrotate.service: Succeeded. Oct 25 00:00:15 raspberrypi systemd[1]: Started Rotate log files. pi@raspberrypi:~ $ ls -la /etc/logrotate.d/* -rw-r--r-- 1 root root 120 Apr 19 2019 /etc/logrotate.d/alternatives -rw-r--r-- 1 root root 173 Apr 19 2021 /etc/logrotate.d/apt -rw-r--r-- 1 root root 130 Aug 29 2018 /etc/logrotate.d/btmp -rw-r--r-- 1 root root 112 Apr 19 2019 /etc/logrotate.d/dpkg -rw-r--r-- 1 root root 501 Feb 26 2019 /etc/logrotate.d/rsyslog -rw-r--r-- 1 root root 145 Feb 19 2018 /etc/logrotate.d/wtmp pi@raspberrypi:~ $ich bin mir allerdings nicht sicher ob ich den rsyslog wieder starten sollte... er wird ja aktuell unter dem Befehl
pi@raspberrypi:~ $ lsof /var/log/kern.lognicht als aktiv aufgeführt, aber das wurde er im Laufe des Tages definitiv einmal.. vermutlich habe ich ihn nach dem stoppen nicht wieder gestartet...?
edit: Was mir noch aufgefallen ist, das ganze Theater begann ja heute morgen als ich den mihome-vacuum adapter einrichten wollte. Wenn ich diesen Deinstallieren möchte, tut er das lt.log auch. Die Instanz und auch die Objekte sind alle weg.. Aber er wird immer noch als installiert unter den Adaptern aufgeführt ...?
Ansonsten läuft und verhält sich der Iobroker wieder ganz normal. -
@erazor86 sagte in Iobroker nicht mehr erreichbar / Festplatte voll?:
n und diesen Post wurde mein zweiter Sohn geboren. Bin gerade ausm Kreissaal zurück, damit hätte ich heute auch nicht mehr gerechnet
Moin,
mein Glückwunsch, und alles Gute für Mama und dem neuen Erdenbürger, dem großen Bruder und natürlich dem Papa.
VG
Bernd -
@erazor86 sagte in Iobroker nicht mehr erreichbar / Festplatte voll?:
Ansonsten läuft und verhält sich der Iobroker wieder ganz normal
Moin,
eigentlich meinte ich nicht, dass Du mir hier die Files für Logrotate noch einmal zeigst, sondern, dass Du Dir diese einmal anschauen solltest, was da drin steht um zu verstehen was Logrotate macht
@erazor86 sagte in Iobroker nicht mehr erreichbar / Festplatte voll?:
ich bin mir allerdings nicht sicher ob ich den rsyslog wieder starten sollte
Wenn Du ihn nicht startest, dann werden einige Logfiles nicht mehr geschrieben, dann wachsen die auch nicht mehr an, aber sollte es ein Problem/Fehler geben, dann hat mal halt auch keine System-Logfiles.
Ist also eine Entscheidung, die Du treffen musst.@erazor86 sagte in Iobroker nicht mehr erreichbar / Festplatte voll?:
Die Instanz und auch die Objekte sind alle weg.. Aber er wird immer noch als installiert unter den Adaptern aufgeführt ...?
Was hast Du genau gemacht?
Wenn Du nur unter dem ReiterInstanzdie Instanz gelöscht hast, dann ist auch nur diese und die dazugehörigen Objekte gelöscht, Du musst auch den Adapter löschen.
Du kannst Dir anschauen, welche Adapter Duinstallierthast und eine oder mehrereInstanz(en)haben
Du kannst Dir anschauen welche Adapter Du
installierthast, die aber keineInstanzhaben
Hier sollte bei Dir noch dermihome-vaccumauftauchen!Und Du hast eine Gesamtübersicht über alle Adapter
Wenn Du nicht nur die Instanz, sondern auch den Adapter löschen möchtest, dann
Man sieht, der Adapter ist noch installiert, hat aber keine Instanz mehr
Jetzt ist er auch unter den Instanz losen Adaptern zu finden
Um den Adapter zu deinstallieren, auf die drei Punkte klicken
Und dann auf den Mülleimer
Du kannst natürlich auch gleich im Adapter auf den Mülleimer klicken, dann werden meistens, erst die Objekte, dann die Instanz, und dann der Adapter gelöscht.
VG
Bernd
