Fehler
- Festplatte mit 0 Bytes - Unsupported sector size 520
- Nextcloud - Terminal Updater - Fehler
- Unifi Controller startet nicht mehr
Festplatte mit 0 Bytes - Unsupported sector size 520
Ich hatte SAS Server Festplatten auf Ebay gekauft, diese hatten eine Sector Größe von 520 statt 512, damit konnte mein Linux Server nicht arbeiten.
Ausgabe von lsblk:
root@thinkstation-d30:/home/jj# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 111,9M 1 loop /snap/lxd/24322
loop1 7:1 0 63,3M 1 loop /snap/core20/1822
loop2 7:2 0 49,8M 1 loop /snap/snapd/18357
sda 8:0 0 232,9G 0 disk
├─sda1 8:1 0 1G 0 part /boot/efi
└─sda2 8:2 0 231,8G 0 part /
sdb 8:80 1 0B 0 disk
sdc 8:80 1 0B 0 disk Wenn man dann in /var/log/syslog guckt:
Mar 2 14:35:49 thinkstation-d30 kernel: [842811.011313] sd 6:0:21:0: [sdb] Unsupported sector size 520.
Mar 2 14:35:49 thinkstation-d30 kernel: [842811.011789] sd 6:0:21:0: [sdb] 0 512-byte logical blocks: (0 B/0 B)
Mar 2 14:35:49 thinkstation-d30 kernel: [842811.011793] sd 6:0:21:0: [sdb] 520-byte physical blocks
Mar 2 14:35:49 thinkstation-d30 kernel: [842811.012135] sd 6:0:21:0: [sdb] Test WP failed, assume Write Enabled
Mar 2 14:35:49 thinkstation-d30 kernel: [842811.012243] sd 6:0:21:0: [sdb] Asking for cache data failed
Mar 2 14:35:49 thinkstation-d30 kernel: [842811.012269] sd 6:0:21:0: [sdb] Assuming drive cache: write through
Mar 2 14:35:49 thinkstation-d30 kernel: [842811.015632] sd 6:0:21:0: [sdb] Spinning up disk...
Mar 2 14:35:49 thinkstation-d30 systemd-udevd[230768]: sdx: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdb' failed with exit code 1.
Mar 2 14:36:19 thinkstation-d30 kernel: [842840.707363] sd 6:0:21:0: [sdb] Unsupported sector size 520.
Mar 2 14:36:19 thinkstation-d30 kernel: [842840.708694] sd 6:0:21:0: [sdb] Write cache: disabled, read cache: enabled, supports DPO and FUA
Mar 2 14:36:19 thinkstation-d30 kernel: [842840.709171] sd 6:0:21:0: [sdb] Attached SCSI disk
Mar 2 14:37:08 thinkstation-d30 kernel: [842841.350666] ................................................
Mar 2 14:37:08 thinkstation-d30 kernel: [842889.668429] ata5: SATA link down (SStatus 0 SControl 300)
Mar 2 14:37:25 thinkstation-d30 kernel: [842890.498005] .................not responding...
Mar 2 14:37:25 thinkstation-d30 kernel: [842906.882025] sd 6:0:22:0: [sdb] Unsupported sector size 520.
Mar 2 14:37:25 thinkstation-d30 kernel: [842906.882508] sd 6:0:22:0: [sdb] 0 512-byte logical blocks: (0 B/0 B)
Mar 2 14:37:25 thinkstation-d30 kernel: [842906.882511] sd 6:0:22:0: [sdb] 520-byte physical blocks
Mar 2 14:37:25 thinkstation-d30 kernel: [842906.882865] sd 6:0:22:0: [sdb] Test WP failed, assume Write Enabled
Mar 2 14:37:25 thinkstation-d30 kernel: [842906.882975] sd 6:0:22:0: [sdb] Asking for cache data failed
Mar 2 14:37:25 thinkstation-d30 kernel: [842906.882998] sd 6:0:22:0: [sdb] Assuming drive cache: write through
Mar 2 14:37:25 thinkstation-d30 kernel: [842906.884748] sd 6:0:22:0: [sdb] Spinning up disk...
Mar 2 14:37:25 thinkstation-d30 systemd-udevd[234836]: sdb: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdb' failed with exit code 1.
Mar 2 14:37:34 thinkstation-d30 kernel: [842907.905767] .........ready
Mar 2 14:37:34 thinkstation-d30 kernel: [842916.098275] sd 6:0:22:0: [sdb] Unsupported sector size 520.
Mar 2 14:37:34 thinkstation-d30 kernel: [842916.099587] sd 6:0:22:0: [sdb] Write cache: disabled, read cache: enabled, supports DPO and FUA
Mar 2 14:37:34 thinkstation-d30 kernel: [842916.100070] sd 6:0:22:0: [sdb] Attached SCSI disk
Mar 2 14:38:39 thinkstation-d30 kernel: [842981.024812] sd 7:0:0:4: [sdj] Media removed, stopped polling
Mar 2 14:39:41 thinkstation-d30 kernel: [843042.682033] sd 6:0:22:0: device_block, handle(0x001b)
Mar 2 14:39:51 thinkstation-d30 kernel: [843052.431519] sd 6:0:22:0: device_unblock and setting to running, handle(0x001b)
Mar 2 14:39:51 thinkstation-d30 kernel: [843052.793769] mpt2sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x5000c5006338f78e)
Mar 2 14:39:51 thinkstation-d30 kernel: [843052.793778] mpt2sas_cm0: removing handle(0x001b), sas_addr(0x5000c5006338f78e)
Mar 2 14:39:51 thinkstation-d30 kernel: [843052.793781] mpt2sas_cm0: enclosure logical id(0x5d4ae524852be97e), slot(14)
Mar 2 14:41:03 thinkstation-d30 kernel: [843124.431788] mpt2sas_cm0: handle(0x1b) sas_address(0x5000c5006338f78e) port_type(0x1)
Mar 2 14:41:03 thinkstation-d30 kernel: [843124.493757] scsi 6:0:23:0: Direct-Access SEAGATE ST910006CLAR1000 AS0C PQ: 0 ANSI: 5
Mar 2 14:41:03 thinkstation-d30 kernel: [843124.493781] scsi 6:0:23:0: SSP: handle(0x001b), sas_addr(0x5000c5006338f78e), phy(14), device_name(0x00c500508ef73863)
Mar 2 14:41:03 thinkstation-d30 kernel: [843124.493784] scsi 6:0:23:0: enclosure logical id (0x5d4ae524852be97e), slot(14)
Mar 2 14:41:03 thinkstation-d30 kernel: [843124.493793] scsi 6:0:23:0: qdepth(254), tagged(1), scsi_level(6), cmd_que(1)
Mar 2 14:41:03 thinkstation-d30 kernel: [843124.493897] scsi 6:0:23:0: Power-on or device reset occurred
Mar 2 14:41:03 thinkstation-d30 kernel: [843124.495280] sd 6:0:23:0: [sdb] Spinning up disk...
Mar 2 14:41:03 thinkstation-d30 kernel: [843124.495417] sd 6:0:23:0: Attached scsi generic sg26 type 0
Mar 2 14:41:03 thinkstation-d30 kernel: [843124.495748] end_device-6:0:22: add: handle(0x001b), sas_addr(0x5000c5006338f78e)Also passt hier die Sector Größe nicht, diese kann man aber mit den Befehl "sg_format" anpassen:
sg_format /dev/disk/by-id/scsi-SSEAGATE_ST910006CLAR1000_9XG86B5W_0000C526KTTB -v --format --size=512Ich habe hier lieber by-id genutzt, da ich mir nicht sicher bin, wie gut sdb da funktioniert hätte und ich eh die Seriennummer auf der Festplatte lesen kann.
Je nach Größe dauert das schon seine paar Stunden, er fragt anfangs noch ein paar mal, ob die Festplatte wirklich gelöscht werden soll.
Wenn man nichts macht, führt er es einfach aus.
Am Ende kommt dann sowas:
Format unit in progress, 99.01% done
Format unit in progress, 99.20% done
Format unit in progress, 99.38% done
Format unit in progress, 99.56% done
Format unit in progress, 99.74% done
Format unit in progress, 99.92% done
FORMAT UNIT Complete
root@thinkstation-d30:/home/jj#In lsblk:
root@thinkstation-d30:/home/jj# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 111,9M 1 loop /snap/lxd/24322
loop1 7:1 0 63,3M 1 loop /snap/core20/1822
loop2 7:2 0 49,8M 1 loop /snap/snapd/18357
sda 8:0 0 232,9G 0 disk
├─sda1 8:1 0 1G 0 part /boot/efi
└─sda2 8:2 0 231,8G 0 part /
sdb 65:112 0 931,5G 0 disk
sdc 65:128 0 931,5G 0 disk Danach kann die Festplatte ganz normal genutzt werden...
Nextcloud - Terminal Updater - Fehler
Fehler:
root@nextcloud:/var/www/html/nextcloud# sudo -u www-data php updater/updater.phar
Nextcloud Updater - version: v26.0.0beta2-9-g64e2e4c dirty
Current version is 27.1.1.
PHP Fatal error: Uncaught Error: Call to undefined function NC\Updater\curl_init() in phar:///var/www/html/nextcloud/updater/updater.phar/lib/Updater.php:468
Stack trace:
#0 phar:///var/www/html/nextcloud/updater/updater.phar/lib/Updater.php(132): NC\Updater\Updater->getUpdateServerResponse()
#1 phar:///var/www/html/nextcloud/updater/updater.phar/lib/UpdateCommand.php(155): NC\Updater\Updater->checkForUpdate()
#2 phar:///var/www/html/nextcloud/updater/updater.phar/vendor/symfony/console/Command/Command.php(255): NC\Updater\UpdateCommand->execute()
#3 phar:///var/www/html/nextcloud/updater/updater.phar/vendor/symfony/console/Application.php(1009): Symfony\Component\Console\Command\Command->run()
#4 phar:///var/www/html/nextcloud/updater/updater.phar/vendor/symfony/console/Application.php(273): Symfony\Component\Console\Application->doRunCommand()
#5 phar:///var/www/html/nextcloud/updater/updater.phar/vendor/symfony/console/Application.php(149): Symfony\Component\Console\Application->doRun()
#6 phar:///var/www/html/nextcloud/updater/updater.phar/updater.php(10): Symfony\Component\Console\Application->run()
#7 /var/www/html/nextcloud/updater/updater.phar(14): require('...')
#8 {main}
thrown in phar:///var/www/html/nextcloud/updater/updater.phar/lib/Updater.php on line 468
root@nextcloud:/var/www/html/nextcloud# root@nextcloud:/var/www/html/nextcloud# sudo -u www-data php updater/updater.phar
Nextcloud Updater - version: v26.0.0beta2-9-g64e2e4c dirty
Current version is 27.1.1.
PHP Fatal error: Uncaught Error: Call to undefined function NC\Updater\simplexml_load_string() in phar:///var/www/html/nextcloud/updater/updater.phar/lib/Updater.php:495
Stack trace:
#0 phar:///var/www/html/nextcloud/updater/updater.phar/lib/Updater.php(132): NC\Updater\Updater->getUpdateServerResponse()
#1 phar:///var/www/html/nextcloud/updater/updater.phar/lib/UpdateCommand.php(155): NC\Updater\Updater->checkForUpdate()
#2 phar:///var/www/html/nextcloud/updater/updater.phar/vendor/symfony/console/Command/Command.php(255): NC\Updater\UpdateCommand->execute()
#3 phar:///var/www/html/nextcloud/updater/updater.phar/vendor/symfony/console/Application.php(1009): Symfony\Component\Console\Command\Command->run()
#4 phar:///var/www/html/nextcloud/updater/updater.phar/vendor/symfony/console/Application.php(273): Symfony\Component\Console\Application->doRunCommand()
#5 phar:///var/www/html/nextcloud/updater/updater.phar/vendor/symfony/console/Application.php(149): Symfony\Component\Console\Application->doRun()
#6 phar:///var/www/html/nextcloud/updater/updater.phar/updater.php(10): Symfony\Component\Console\Application->run()
#7 /var/www/html/nextcloud/updater/updater.phar(14): require('...')
#8 {main}
thrown in phar:///var/www/html/nextcloud/updater/updater.phar/lib/Updater.php on line 495
root@nextcloud:/var/www/html/nextcloud# Bei mir fehlte php-curl und php-xml, also musste ich das nach installieren:
sudo apt-get install php-curl php-xmlDanach lief er bei mir:
root@nextcloud:/var/www/html/nextcloud# sudo -u www-data php updater/updater.phar
Nextcloud Updater - version: v26.0.0beta2-9-g64e2e4c dirty
Current version is 27.1.1.
Update to Nextcloud 27.1.7 available. (channel: "stable")
Following file will be downloaded automatically: https://download.nextcloud.com/server/releases/nextcloud-27.1.7.zip
Open changelog ↗
Steps that will be executed:
[ ] Check for expected files
[ ] Check for write permissions
[ ] Create backup
[ ] Downloading
[ ] Verify integrity
[ ] Extracting
[ ] Enable maintenance mode
[ ] Replace entry points
[ ] Delete old files
[ ] Move new files in place
[ ] Done
Start update? [y/N] Y
Info: Pressing Ctrl-C will finish the currently running step and then stops the updater.
[✔] Check for expected files
[✔] Check for write permissions
[ ] Create backup ...
Fehler zwei, es fehlte hier die Zip Erweiterung:
Info: Pressing Ctrl-C will finish the currently running step and then stops the updater.
[✔] Check for expected files
[✔] Check for write permissions
[✔] Create backup
[✔] Downloading
[✔] Verify integrity
[ ] Extracting ...PHP Fatal error: Uncaught Error: Class "ZipArchive" not found in phar:///var/www/html/nextcloud/updater/updater.phar/lib/Updater.php:693
Stack trace:
#0 phar:///var/www/html/nextcloud/updater/updater.phar/lib/UpdateCommand.php(383): NC\Updater\Updater->extractDownload()
#1 phar:///var/www/html/nextcloud/updater/updater.phar/lib/UpdateCommand.php(240): NC\Updater\UpdateCommand->executeStep()
#2 phar:///var/www/html/nextcloud/updater/updater.phar/vendor/symfony/console/Command/Command.php(255): NC\Updater\UpdateCommand->execute()
#3 phar:///var/www/html/nextcloud/updater/updater.phar/vendor/symfony/console/Application.php(1009): Symfony\Component\Console\Command\Command->run()
#4 phar:///var/www/html/nextcloud/updater/updater.phar/vendor/symfony/console/Application.php(273): Symfony\Component\Console\Application->doRunCommand()
#5 phar:///var/www/html/nextcloud/updater/updater.phar/vendor/symfony/console/Application.php(149): Symfony\Component\Console\Application->doRun()
#6 phar:///var/www/html/nextcloud/updater/updater.phar/updater.php(10): Symfony\Component\Console\Application->run()
#7 /var/www/html/nextcloud/updater/updater.phar(14): require('...')
#8 {main}
thrown in phar:///var/www/html/nextcloud/updater/updater.phar/lib/Updater.php on line 693
root@nextcloud:/var/www/html/nextcloud# Also muss hier zip für php noch installiert werden:
sudo apt-get install php-zip
Unifi Controller startet nicht mehr
Fehler - /var/log/unifi/server.log :
[2024-03-07 03:17:19,025] <db-server> INFO db - Checking if database needs to be shut down
[2024-03-07 03:17:20,026] <db-server> INFO db - Database was not running
[2024-03-07 03:17:20,026] <db-server> INFO db - Database configuration, dir=/usr/lib/unifi/data/db, port=27117
[2024-03-07 03:17:20,114] <db-server> ERROR system - unable to exec
java.io.IOException: Cannot run program "bin/mongod" (in directory "/usr/lib/unifi"): error=0, Failed to exec spawn helper: pid: 755101, signal: 11
at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1143)
at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1073)
at com.ubnt.ace.B.Ôo0000(Unknown Source)
at com.ubnt.ace.B.Öô0000(Unknown Source)
at com.ubnt.ace.B.oÖ0000(Unknown Source)
at com.ubnt.service.system.z.Òô0000(Unknown Source)
at com.ubnt.service.system.z$1.run(Unknown Source)
at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: java.io.IOException: error=0, Failed to exec spawn helper: pid: 755101, signal: 11
at java.base/java.lang.ProcessImpl.forkAndExec(Native Method)
at java.base/java.lang.ProcessImpl.<init>(ProcessImpl.java:314)
at java.base/java.lang.ProcessImpl.start(ProcessImpl.java:244)
at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1110)
... 7 common frames omitted
[2024-03-07 03:17:20,114] <db-server> INFO db - Starting database process...
[2024-03-07 03:17:20,205] <db-server> ERROR system - unable to exec
java.io.IOException: Cannot run program "bin/mongod" (in directory "/usr/lib/unifi"): error=0, Failed to exec spawn helper: pid: 755109, signal: 11
at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1143)
at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1073)
at com.ubnt.ace.B.ô00000(Unknown Source)
at com.ubnt.ace.B.oÔ0000(Unknown Source)
at com.ubnt.service.system.z.Òô0000(Unknown Source)
at com.ubnt.service.system.z$1.run(Unknown Source)
at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: java.io.IOException: error=0, Failed to exec spawn helper: pid: 755109, signal: 11
at java.base/java.lang.ProcessImpl.forkAndExec(Native Method)
at java.base/java.lang.ProcessImpl.<init>(ProcessImpl.java:314)
at java.base/java.lang.ProcessImpl.start(ProcessImpl.java:244)
at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1110)
... 6 common frames omitted
[2024-03-07 03:17:20,205] <db-server> INFO db - Database process stopped...
[2024-03-07 03:17:21,904] <stamgr> WARN cache - unable to retrieve settings in site 6432ba9476f22131549ac718
com.google.common.util.concurrent.UncheckedExecutionException: com.mongodb.MongoTimeoutException: Timed out after 10000 ms while waiting to connect. Client view of cluster state is {type=UNKNOWN, servers=[{address=localhost:27117, type=UNKNOWN, state=CONNECTING, exception={com.mongodb.MongoSocketOpenException: Exc>
at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2055)
at com.google.common.cache.LocalCache.get(LocalCache.java:3966)
at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3989)
at com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4950)
at com.ubnt.service.system.OooO.ôöØ000(Unknown Source)
at com.ubnt.service.system.OooO.oøØ000(Unknown Source)
at com.ubnt.service.event.A.newreturnnew(Unknown Source)
at com.ubnt.service.event.A.oöÓ000(Unknown Source)
at com.ubnt.service.event.A.ÔõÓ000(Unknown Source)
at com.ubnt.service.devmgr.classObject.StringdoObject(Unknown Source)
at com.ubnt.service.system.newnew.ÖO0000(Unknown Source)
at com.ubnt.ace.B$_OOo.run(Unknown Source)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: com.mongodb.MongoTimeoutException: Timed out after 10000 ms while waiting to connect. Client view of cluster state is {type=UNKNOWN, servers=[{address=localhost:27117, type=UNKNOWN, state=CONNECTING, exception={com.mongodb.MongoSocketOpenException: Exception opening socket}, caused by {java.net.ConnectE>
at com.mongodb.internal.connection.BaseCluster.getDescription(BaseCluster.java:180)
at com.mongodb.internal.connection.SingleServerCluster.getDescription(SingleServerCluster.java:44)
at com.mongodb.client.internal.MongoClientDelegate.getConnectedClusterDescription(MongoClientDelegate.java:144)
at com.mongodb.client.internal.MongoClientDelegate.createClientSession(MongoClientDelegate.java:101)
at com.mongodb.client.internal.MongoClientDelegate$DelegateOperationExecutor.getClientSession(MongoClientDelegate.java:291)
at com.mongodb.client.internal.MongoClientDelegate$DelegateOperationExecutor.execute(MongoClientDelegate.java:183)
at com.mongodb.client.internal.FindIterableImpl.first(FindIterableImpl.java:213)
at com.ubnt.service.system.z.Stringnull(Unknown Source)
at com.ubnt.service.system.z.Ó00000(Unknown Source)
at com.ubnt.service.system.floatsuper.ØÕ0000(Unknown Source)
at com.ubnt.service.system.OooO$2.o00000(Unknown Source)
at com.ubnt.service.system.OooO$2.load(Unknown Source)
at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3533)
at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2282)
at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2159)
at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2049)
... 17 common frames omitted
[2024-03-07 03:17:21,904] <stamgr> INFO db - waiting for db connection...
[2024-03-07 03:17:22,011] <discover> INFO discover - [Internal] incomplete device information received
com.mongodb.MongoTimeoutException: Timed out after 10000 ms while waiting to connect. Client view of cluster state is {type=UNKNOWN, servers=[{address=localhost:27117, type=UNKNOWN, state=CONNECTING, exception={com.mongodb.MongoSocketOpenException: Exception opening socket}, caused by {java.net.ConnectException: C>
at com.mongodb.internal.connection.BaseCluster.getDescription(BaseCluster.java:180)
at com.mongodb.internal.connection.SingleServerCluster.getDescription(SingleServerCluster.java:44)
at com.mongodb.client.internal.MongoClientDelegate.getConnectedClusterDescription(MongoClientDelegate.java:144)
at com.mongodb.client.internal.MongoClientDelegate.createClientSession(MongoClientDelegate.java:101)
at com.mongodb.client.internal.MongoClientDelegate$DelegateOperationExecutor.getClientSession(MongoClientDelegate.java:291)
at com.mongodb.client.internal.MongoClientDelegate$DelegateOperationExecutor.execute(MongoClientDelegate.java:183)
at com.mongodb.client.internal.FindIterableImpl.first(FindIterableImpl.java:213)
at com.ubnt.service.system.z.Stringnull(Unknown Source)
at com.ubnt.service.system.z.Ó00000(Unknown Source)
at com.ubnt.service.devmgr.o0O0o.Õôö000(Unknown Source)
at com.ubnt.service.devmgr.o0O0o.thisinterfaceString(Unknown Source)
at com.ubnt.net.float.ÔÒø000(Unknown Source)
at com.A.A.oOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO.Object.ô00000(Unknown Source)
at com.A.A.oOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO.oOoO$1.run(Unknown Source)
at java.base/java.lang.Thread.run(Thread.java:833)
[2024-03-07 03:17:22,011] <discover> INFO db - waiting for db connection...Der Fehler sagt aus, das er Probleme mit der mongo db also der Datenbank gibt.
Zuerst muss der Dienst gestoppt werden:
service unifi stopIn einigen Fällen, in denen das Journal beschädigt ist, ist es hilfreich, den folgenden Befehl auszuführen, bevor die Datenbank repariert wird, um sie an einen anderen Ort zu verschieben
mv -vi /usr/lib/unifi/data/db/journal /usr/lib/unifi/data/db/journal-$(date -I)Reparieren Sie die Datenbank mit diesem Befehl:
mongod --dbpath /usr/lib/unifi/data/db --logpath /usr/lib/unifi/logs/mongod.log --repairStarten Sie schließlich den UniFi-Dienst neu
service unifi startHinweis: Wenn dieser Prozess als Root durchgeführt wurde, hat sich der Dateibesitz möglicherweise geändert. Dies kann geändert werden mit:
chown -R unifi:unifi /usr/lib/unifi/data/db/
chown -R unifi:unifi /usr/lib/unifi/logs/