reboot – Computer sometimes cuts power during restart

What would you do to troubleshoot this?

Booting my system requires unlocking the drive (OPAL SED w/PBA), then restarting. If the computer (more specifically the drive) loses power during the restart, the drive is locked again, meaning I have to enter the password again. I get stuck on this loop at least four times these days. Eventually, it always works, but I fear it’s getting worse.

All of the hardware is 6-7 years old, but high end. I’ve never once noticed the platinum power supply turning on its fan, and I’ve never smelled anything like a burnt capacitor out of it. With how reliably everything else works, I can’t imagine there being a serious motherboard fault either.

Perhaps a year ago, I did a thorough cleaning, wiping down non-electronic surfaces and using compressed air in some places. I hadn’t used the system much since – I’m a remote worker preferring to use my laptop. The COVID-19 situation has left me at home constantly, so I found myself wanting to use the more powerful desktop, meaning I really started to notice the problem.

One theory so far: something is worn out, or damaged by icy compressed air, and some electronic junction needs to get hot in order to carry current reliably. The multiple restarts may be leaving time for it to warm up. This sounds far fetched, but it’s all I’ve got.

power management – Restart TLP service without rebooting system

TLP helps make my laptop more conservative on power when on battery power, and more performance focused when on AC. The issue is that when I want to enable/disable TLP or change some settings with TLPUI, it requires a reboot before it takes affect. I’ve tried sudo systemctl stop TLP and sudo systemctl start TLP, but this doesn’t seem to have any effect.

pnp powershell: restart the index of part of a document library or files of a certain extension in Sharepoint Online

I have a gigantic set of document libraries that contain a folder with msg files. I set some managed properties specifically for folders with msg files to do custom filter for these properties in search center. Search and filters work, but only newly entered msg files are being collected. The previously entered msg file properties are not present in the newly managed new property indexes. I want to trigger a trace of only these subfolders, which have the same name and are nested within larger document libraries. Is there a way to do this using PnP? I already tried using Request-PnPReindexList -Identity "list / sublist". There was no error, but more than 24 hours have passed and the list has not been indexed.

I also tried reindexing one of the full document libraries using the advanced configuration of the front-end library SP> reindex library. About three days have passed and it has not been re-indexed yet. I'd rather set up reindexing only the msg file subfolders so as not to overwhelm the system, which has many terabytes of documents divided into dozens of libraries. Thanks in advance for any advice you can provide.

When asking a taxi in THA to wait for me for a few minutes during a stop in our trip, is the taxi supposed to restart the meter or keep it running?

When asking a taxi in Bangkok, Thailand to wait for me for a few minutes during a stop in our trip, is the taxi supposed to restart the meter (starts at 35 THB) when I go back to the taxi, or keep the meter running?

Restart the server HP DL380p G8 after turning on immediately

When turning on the server (HP DL 380p G8), after displaying the BIOS version the server immediately will reset.
I don’t have any option to choose ( for example F8, F9, F10,…)

what I should to do?

Windows wants to install an old version even though i have the latest one, already downloaded it just needs restart, how do i know if it’s safe?

Here is the screenshot of my updates history/status.

https://www.dropbox.com/s/n0x2zvix5nh99zg/Screenshot%20%281%29.png?dl=0

Here in this dropbox picture there are 2 comments with all the info.

centos – Redis don’t stop or restart on CentOS7

I’ve installed Redis version 3.2.12 on one CentOS 7 node of a cluster with Cloudera Manager 6.3 and my redis never stop. I want to add a password but it don’t want to restart.
Everything is on default, I just added the password, but that has no effects because I can’t restart.

My instalation was:

sudo yum -y install redis

sudo service redis start

When I type redis-cli, CLI starts normally at 127.0.0.1:6379. when I try shutdown, the console shows ‘not connected’, but with lsof -i :6379 I can identify that the ‘redis-service’ jobs die and return with another PID, celery jobs always stay alive.
If I try to kill celery and redis jobs, it always return with another PID. There are aproximately 67 jobs reunning.

service redis stop Return ‘Redirecting to /bin/systemctl stop redis.service’ but has no effects.

If I try service redis restart then service redis status it returns:

redis.service: main process exited, code=exited, status=1/FAILURE
Unit redis.service entered failed state.

Option daemonize is no

Someone can please help me as a way to debug or understand what is happening? It’s my first time with Redis.

ipados: iPad wifi option appears gray after Bluetooth caused it to get stuck in a restart cycle

My iPad was updated and the bluetooth function stopped working. I discovered it with a crash log with 3utools. At first, it would crash and restart, only to do the same. Once I was able to access the settings fast enough to disable Bluetooth, and although it still rebooted, it ran stable at startup, except that the WiFI option was fully grayed out, and Bluetooth, when enabled through settings, was simply a spinning cog wheel. Occasionally after rebooting it will sometimes connect to WiFi; However, this only happens for a few moments at a time, which makes me hesitate a bit when saying that it's just hardware. Here is the last record:

Incident identifier: 7251F755-B883-4927-BCAC-9C7BEFC95DF4
CrashReporter Key: aa4ee93a47dfe616a58f2199f2d969d65e8e25bc
Hardware model: iPad7.3
Process: bluetoothd (77)
Path: / usr / sbin / bluetoothd
Identifier: bluetoothd
Version: ???
Code type: ARM-64 (Native)
Role: not specified
Main process: launchd (1)
Coalition: com.apple.bluetoothd (111)

Date / time: 2020-05-14 22: 44: 20.2982 -0400
Release time: 2020-05-14 22: 43: 42.9511 -0400
Operating system version: iPhone OS 13.4.1 (17E262)
Launch Type: User
Baseband version: n / a
Report version: 104

Exception type: EXC_CRASH (SIGABRT)
Exception codes: 0x0000000000000000, 0x0000000000000000
Exception note: EXC_CORPSE_NOTIFY
Wire activated: 7

Thread name 0: Dispatch queue: com.apple.main-thread
Thread 0:
0 libsystem_kernel.dylib 0x00000001b27f3198 0x1b27ef000 + 16792
1 libsystem_kernel.dylib 0x00000001b27f260c 0x1b27ef000 + 13836
2 CoreFoundation 0x00000001b299d3b4 0x1b28f5000 + 689076
3 CoreFoundation 0x00000001b29983e8 0x1b28f5000 + 668648
4 CoreFoundation 0x00000001b2997c34 0x1b28f5000 + 666676
5 CoreFoundation 0x00000001b2998990 0x1b28f5000 + 670096
6 bluetoothd 0x0000000100a2aeb8 0x100a1c000 + 61112
7 libdyld.dylib 0x00000001b281f800 0x1b281e000 + 6144

Thread 1:
0 libsystem_pthread.dylib 0x00000001b2739738 0x1b272b000 + 59192

Thread 2:
0 libsystem_pthread.dylib 0x00000001b2739738 0x1b272b000 + 59192

Thread name 3: send queue: com.apple.bluetooth.root
Thread 3:
0 libsystem_kernel.dylib 0x00000001b2815104 0x1b27ef000 + 155908
1 libsystem_c.dylib 0x00000001b267d458 0x1b260e000 + 455768
2 libsystem_c.dylib 0x00000001b267d328 0x1b260e000 + 455464
3 bluetoothd 0x0000000100ac73a4 0x100a1c000 + 701348
4 bluetoothd 0x0000000100a705d0 0x100a1c000 + 345552
5 bluetoothd 0x0000000100cba864 0x100a1c000 + 2746468
6 bluetoothd 0x0000000100cbb738 0x100a1c000 + 2750264
7 bluetoothd 0x0000000100ca39a4 0x100a1c000 + 2652580
8 libdispatch.dylib 0x00000001b26e49a8 0x1b268a000 + 371112
9 libdispatch.dylib 0x00000001b26e5524 0x1b268a000 + 374052
10 libdispatch.dylib 0x00000001b26918a4 0x1b268a000 + 30884
11 libdispatch.dylib 0x00000001b26922c4 0x1b268a000 + 33476
12 libdispatch.dylib 0x00000001b269b78c 0x1b268a000 + 71564
13 libsystem_pthread.dylib 0x00000001b2736b74 0x1b272b000 + 47988
14 libsystem_pthread.dylib 0x00000001b2739740 0x1b272b000 + 59200

Thread 4:
0 libsystem_pthread.dylib 0x00000001b2739738 0x1b272b000 + 59192

Thread 5:
0 libsystem_pthread.dylib 0x00000001b2739738 0x1b272b000 + 59192

Thread name 6: StackLoop
Thread 6:
0 libsystem_kernel.dylib 0x00000001b2814b58 0x1b27ef000 + 154456
1 libsystem_pthread.dylib 0x00000001b272ed18 0x1b272b000 + 15640
2 bluetoothd 0x0000000100a70840 0x100a1c000 + 346176
3 libsystem_pthread.dylib 0x00000001b2735d98 0x1b272b000 + 44440
4 libsystem_pthread.dylib 0x00000001b273974c 0x1b272b000 + 59212

Thread name 7: RxLoop
Thread 7 starry:
0 libsystem_kernel.dylib 0x00000001b2814d88 0x1b27ef000 + 155016
1 libsystem_pthread.dylib 0x00000001b272d1e8 0x1b272b000 + 8680
2 libsystem_c.dylib 0x00000001b2680644 0x1b260e000 + 468548
3 bluetoothd 0x0000000100e05a24 0x100a1c000 + 4102692
4 bluetoothd 0x0000000100a59200 0x100a1c000 + 250368
5 bluetoothd 0x0000000100a577f0 0x100a1c000 + 243696
6 libsystem_pthread.dylib 0x00000001b2735d98 0x1b272b000 + 44440
7 libsystem_pthread.dylib 0x00000001b273974c 0x1b272b000 + 59212

Thread 7 crashed with status of ARM thread (64 bit):
x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x0000000000000000 x3: 0x0000000000000000
x4: 0x000000000000002c x5: 0x0000000000000000 x6: 0x0000000000000000 x7: 0x00000000000003f8
x8: 0x000000016f69b000 x9: 0x7bf970bab03f4aec x10: 0x00000001b272d160 x11: 0x02000000100001e8
x12: 0x0000000000000000 x13: 0x02000001100001e8 x14: 0x0000000000000000 x15: 0x0000000000000000
x16: 0x0000000000000148 x17: 0x000000016f69b0e0 x18: 0x0000000000000000 x19: 0x0000000000000006
x20: 0x0000000000013a0f x21: 0x0000000000000001 x22: 0x000000016f69b0e0 x23: 0x0000000100f88000
x24: 0x0000000100e8114e x25: 0x0000000100f9ad40 x26: 0x0000000000000005 x27: 0x0000000100f9a000
x28: 0x0000000100e753e6 fp: 0x000000016f69ad60 lr: 0x00000001b272d1e8
sp: 0x000000016f69ad40 pc: 0x00000001b2814d88 cpsr: 0x40000000
esr: 0x56000080 Address size error

Any ideas?

Does Ubuntu 18.04LTS suddenly restart once the update app is pressed?

Ubuntu 18.04LTS, suddenly restarted once the update app was pressed?

It is an AMD Ryzen 5 2600 CPU, with Gigabyte AB350M-Gaming 3 motherboard with the latest BIOS installed.

I tried to update it to 20.04LTS, but I only had the option to update to 19.10, I saw Ubuntu 20.04 Update Guide: Could there be a corrupt update when I tried to update the machine a few days ago, but it didn't say at the time that there were errors?

Is it your way to see if there is a bug in the syslog or other diagnostic tools built into Ubuntu 18.04?

Thank you

networking: Fedora in VMWare requires sudo dhclient on restart

I am running fedora 31 inside a vmware box on a Windows 10 host as my development machine (I am a software developer). Every time I reboot, my box doesn't have internet access and I have to run $ sudo dhclient. Any ideas on how to fix this? I don't even know where to start.

I run the box in NAT, but none of the network options makes the difference (for example, bridged, host only, etc.).

Apparently, it also started happening randomly. One day, there is simply no internet.

Thank you!

$  uname -a
Linux localhost.localdomain 5.5.11-200.fc31.x86_64 #1 SMP Mon Mar 23 17:32:43 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux