主页 / ubuntu / 问题

问题[restart](ubuntu)

Martin Hope
user1041353
Asked: 2021-09-01 05:55:31 +0800 CST
  • 0

每次启动和重新启动后，我的 Ubuntu 21.04 都可以正常工作。然而 3-4 小时后，它“冻结”了。除了强制重启没有任何帮助。如何避免后者？

终端运行：

<free -h
              total        used        free      shared  buff/cache   available
Mem:          3.5Gi       2.2Gi       243Mi       278Mi       1.1Gi       832Mi
Swap:         2.0Gi        17Mi       2.0Gi

vm.swappiness = 60

Filename                Type        Size    Used    Priority
/swapfile                               file        2097148 17772   -2

top - 09:32:34 up 26 min,  1 user,  load average: 0.26, 0.59, 1.18
Tasks: 203 total,   3 running, 200 sleeping,   0 stopped,   0 zombie
%Cpu(s): 42.9 us,  0.0 sy,  0.0 ni, 57.1 id,  0.0 wa,  0.0 hi,  0.0 si,  0top - 09:33:54 up 27 min,  1 user,  load average: 0.72, 0.73, 1.18
Tasks: 203 total,   3 running, 200 sleeping,   0 stopped,   0 zombie
%Cpu(s): 25.0 us, 18.8 sy,  0.0 ni, 56.2 id,  0.0 wa,  0.0 hi,  0.0 si, top - 09:33:54 up 27 min,  1 user,  load average: 0.72, 0.73, 1.18
Tasks: 203 total,   4 running, 199 sleeping,   0 stopped,   0 zombie
%Cpu(s): 40.0 us, 20.0 sy,  0.0 ni, 40.0 id,  0.0 wa,  0.0 hi,  0.0 si,top - 09:33:54 up 27 min,  1 user,  load average: 0.72, 0.73, 1.18
Tasks: 203 total,   2 running, 201 sleeping,   0 stopped,   0 zombie
%Cpu(s): 33.3 us, 33.3 sy,  0.0 ni, 33.3 id,  0.0 wa,  0.0 hi,  0.0 si,top - 09:33:54 up 27 min,  1 user,  load average: 0.72, 0.73, 1.18
Tasks: 203 total,   5 running, 198 sleeping,   0 stopped,   0 zombie
%Cpu(s): 28.6 us, 42.9 sy,  0.0 ni, 28.6 id,  0.0 wa,  0.0 hi,  0.0 si,
MiB Mem :   3623.3 total,    139.9 free,   2286.0 used,   1197.4 buff/c
MiB Swap:   2048.0 total,   2029.4 free,     18.6 used.    822.0 avail> 


# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=28539ebd-a6e3-4fa7-8dcc-8bdc31b0f505 /               ext4    errors=remount-ro 0       1
/swapfile                                 none            swap    sw

首先，最有价值的东西应该放在硬盘上（例如 Transcend），并且每天都在修改（关闭 Internet）。准备好安装工具。当冻结不好并且无法获得建议时，请强制关闭，插入安装工具，然后按F2启动。从启动菜单中，选择上述工具并重新安装系统。首选 LTS 版本。介意 Livepatch。这在我的情况下有效。

restart
Martin Hope
Yan Tavares
Asked: 2020-08-22 17:05:20 +0800 CST
  • 50

所以我在我的笔记本上配置 VS 代码时，突然我注意到我的界面字体在我的桌面、终端和文件上变得非常小。

我使用 Gnome Tweaks Tool 将缩放因子增加到 1,15 ，但是，即使它处于活动状态，字体仍然很小。

我找到的解决方案是移动缩放因子，它立即解决了我的字体问题，但是，每次我重新启动笔记本时，字体都会再次变小，我必须重复这个过程。

我尝试使用此命令重置我的字体配置，但没有成功。

gsettings reset org.gnome.desktop.interface text-scaling-factor

我也尝试使用命令

dconf reset -f /

最后，我尝试使用 dconf-editor，但仍然没有成功更改字体渲染 DPI 或更改缩放因子。

我提到的所有步骤都暂时修复了我的字体，但是当我重新启动笔记本时问题仍然存在

我没有想法，甚至考虑现在安装一个全新的 Ubuntu ......

我的显卡：NVIDIA GeForce GTX 1050 GPU

nvidia fonts interface restart
Martin Hope
Seamus
Asked: 2020-06-10 00:22:14 +0800 CST
  • 10

这让我觉得有点混乱，但我是 Ubuntu 的新手。我想在关闭或注销 Ubuntu 20.04 时选择恢复打开的应用程序。像往常一样，我搜索了一下，发现有两篇文章说的基本相同：“dconf-tools用于此”（HTG文章，LinOxide文章）。

尝试使用 安装此工具时apt，我得知该dconf-tools软件包不可用。好的 - 所以有什么东西可以代替它 - 对吧？“也许不是”是这里的答案；该答案的作者表示它“从未运作良好”？也有人建议它Window Session Manager很好且维护良好......但他也说整个概念从来没有运作良好？！另一个问答建议dconf-tools有一个替换dconf-cli- 除了用作另一个包中的依赖项，所以......？

另外 - 通过应用程序快速搜索Ubuntu Software显示有一个名为 的应用程序Dconf Editor，但它的描述如此简洁以至于毫无用处。

由于我没有看到 20.04 的任何内容，我认为值得再次提出这个问题：如何从我上次会话中恢复打开的窗口和应用程序？或者，换了dconf-tools什么？

gnome dconf restart 20.04
Martin Hope
Geoffroy
Asked: 2020-05-18 17:01:51 +0800 CST
  • 1

在尝试更新我的 SSL 证书后，我目前的网站出现问题。

我已经完成了本教程中提到的所有步骤：https ://www.digitalocean.com/community/tutorials/how-to-install-an-ssl-certificate-from-a-commercial-certificate-authority

在最后一部分，当我必须输入sudo service apache2 restart行时，我收到了以下错误消息：

Job for apache2.service failed because the control process exited with error code.
See "systemctl status apache2.service" and "journalctl -xe" for details.


systemctl 状态 apache2.service

● apache2.service - The Apache HTTP Server
   Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
  Drop-In: /lib/systemd/system/apache2.service.d
           └─apache2-systemd.conf
   Active: failed (Result: exit-code) since Mon 2020-05-18 00:18:34 UTC; 6s ago
  Process: 4867 ExecStop=/usr/sbin/apachectl stop (code=exited, status=0/SUCCESS)
  Process: 7254 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)
 Main PID: 1045 (code=exited, status=0/SUCCESS)

May 18 00:18:34 systemd[1]: Starting The Apache HTTP Server...
May 18 00:18:34 apachectl[7254]: Action 'start' failed.
May 18 00:18:34 apachectl[7254]: The Apache error log may have more information.
May 18 00:18:34 systemd[1]: apache2.service: Control process exited, code=exited status=1
May 18 00:18:34 systemd[1]: apache2.service: Failed with result 'exit-code'.
May 18 00:18:34 systemd[1]: Failed to start The Apache HTTP Server.
apache2ctl configtest
Syntax OK
apachectl configtest
Syntax OK

我尝试了configtest命令来查看是否有任何合成器错误，但一切似乎都很好。

journalctl -xe

May 18 15:33:52 sshd[31542]: Failed password for i
May 18 15:33:53 sudo[31549]:     root : TTY=pts/0
May 18 15:33:53 sudo[31549]: pam_unix(sudo:session
May 18 15:33:53 systemd[1]: Starting The Apache HT
-- Subject: Unit apache2.service has begun start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit apache2.service has begun starting up.
May 18 15:33:53 apachectl[31555]: Action 'start' f
May 18 15:33:53 apachectl[31555]: The Apache error
May 18 15:33:53 systemd[1]: apache2.service: Contr
May 18 15:33:53 systemd[1]: apache2.service: Faile
May 18 15:33:53 systemd[1]: Failed to start The Ap
-- Subject: Unit apache2.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit apache2.service has failed.
--
-- The result is RESULT.
May 18 15:33:53 sudo[31549]: pam_unix(sudo:session
May 18 15:33:55 kernel: [UFW BLOCK] IN=eth0 OUT= M
lines 1128-1150/1150 (END)
May 18 15:33:52 sshd[31542]: Failed password for invalid user bdt from 206.18
May 18 15:33:53 sudo[31549]:     root : TTY=pts/0 ; PWD=/root ; USER=root ; C
May 18 15:33:53 sudo[31549]: pam_unix(sudo:session): session opened for user
May 18 15:33:53 systemd[1]: Starting The Apache HTTP Server...
-- Subject: Unit apache2.service has begun start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit apache2.service has begun starting up.
May 18 15:33:53 apachectl[31555]: Action 'start' failed.
May 18 15:33:53 apachectl[31555]: The Apache error log may have more informat
May 18 15:33:53 systemd[1]: apache2.service: Control process exited, code=exi
May 18 15:33:53 systemd[1]: apache2.service: Failed with result 'exit-code'.
May 18 15:33:53 systemd[1]: Failed to start The Apache HTTP Server.
-- Subject: Unit apache2.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit apache2.service has failed.
--
-- The result is RESULT.
May 18 15:33:53 sudo[31549]: pam_unix(sudo:session): session closed for user
May 18 15:33:55 kernel: [UFW BLOCK] IN=eth0 OUT= MAC=fa:52:65:0e:6a:71:fe:00:
~
~
~
~
~
~
~
~
~
~
~
lines 1128-1150/1150 (END)
May 18 15:33:52  sshd[31542]: Failed password for invalid user bdt from 206.189.212.33 port 38420 ssh2
May 18 15:33:53  sudo[31549]:     root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/usr/sbin/service ap
May 18 15:33:53  sudo[31549]: pam_unix(sudo:session): session opened for user root by root(uid=0)
May 18 15:33:53  systemd[1]: Starting The Apache HTTP Server...
-- Subject: Unit apache2.service has begun start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit apache2.service has begun starting up.
May 18 15:33:53  apachectl[31555]: Action 'start' failed.
May 18 15:33:53  apachectl[31555]: The Apache error log may have more information.
May 18 15:33:53  systemd[1]: apache2.service: Control process exited, code=exited status=1
May 18 15:33:53  systemd[1]: apache2.service: Failed with result 'exit-code'.
May 18 15:33:53  systemd[1]: Failed to start The Apache HTTP Server.
-- Subject: Unit apache2.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit apache2.service has failed.
--
-- The result is RESULT.
May 18 15:33:53  sudo[31549]: pam_unix(sudo:session): session closed for user root
May 18 15:33:55  kernel: [UFW BLOCK] IN=eth0 OUT= MAC=fa:52:65:0e:6a:71:fe:00:00:00:01:01:08:00 SRC=185.1
~
~
~
~
~
~
~
~
~
~
~
~
lines 1128-1150/1150 (END)
May 18 15:33:52  sshd[31542]: Failed password for invalid user bdt from 206.189.212.33 port 38420 ssh2
May 18 15:33:53  sudo[31549]:     root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/usr/sbin/service apache2 restart
May 18 15:33:53  sudo[31549]: pam_unix(sudo:session): session opened for user root by root(uid=0)
May 18 15:33:53  systemd[1]: Starting The Apache HTTP Server...
-- Subject: Unit apache2.service has begun start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit apache2.service has begun starting up.
May 18 15:33:53  apachectl[31555]: Action 'start' failed.
May 18 15:33:53  apachectl[31555]: The Apache error log may have more information.
May 18 15:33:53  systemd[1]: apache2.service: Control process exited, code=exited status=1
May 18 15:33:53  systemd[1]: apache2.service: Failed with result 'exit-code'.
May 18 15:33:53  systemd[1]: Failed to start The Apache HTTP Server.
-- Subject: Unit apache2.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit apache2.service has failed.
--
-- The result is RESULT.
May 18 15:33:53  sudo[31549]: pam_unix(sudo:session): session closed for user root
May 18 15:33:55  kernel: [UFW BLOCK] IN=eth0 OUT= MAC=fa:52:65:0e:6a:71:fe:00:00:00:01:01:08:00 SRC=185.151.242.187 DST=167.99.179.159 LEN=40 T
~
~
~
~
~
~
~
~
~
~
~
~
lines 1128-1150/1150 (END)
May 18 15:33:52  sshd[31542]: Failed password for invalid user bdt from 206.189.212.33 port 38420 ssh2
May 18 15:33:53  sudo[31549]:     root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/usr/sbin/service apache2 restart
May 18 15:33:53  sudo[31549]: pam_unix(sudo:session): session opened for user root by root(uid=0)
May 18 15:33:53  systemd[1]: Starting The Apache HTTP Server...
-- Subject: Unit apache2.service has begun start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit apache2.service has begun starting up.
May 18 15:33:53  apachectl[31555]: Action 'start' failed.
May 18 15:33:53  apachectl[31555]: The Apache error log may have more information.
May 18 15:33:53  systemd[1]: apache2.service: Control process exited, code=exited status=1
May 18 15:33:53  systemd[1]: apache2.service: Failed with result 'exit-code'.
May 18 15:33:53  systemd[1]: Failed to start The Apache HTTP Server.
-- Subject: Unit apache2.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit apache2.service has failed.
--
-- The result is RESULT.
May 18 15:33:53  sudo[31549]: pam_unix(sudo:session): session closed for user root
May 18 15:33:55  kernel: [UFW BLOCK] IN=eth0 OUT= MAC=fa:52:65:0e:6a:71:fe:00:00:00:01:01:08:00 SRC=185.151.242.187 DST=167.99.179.159 LEN=40 TOS=0x00 PREC=0x00 TTL=240 ID=15380 PROTO=TCP
~
~
~
~
~
~
~
~
~
~
~
~
lines 1128-1150/1150 (END)
May 18 15:33:52  sshd[31542]: Failed password for invalid user bdt from 206.189.212.33 port 38420 ssh2
May 18 15:33:53  sudo[31549]:     root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/usr/sbin/service apache2 restart
May 18 15:33:53  sudo[31549]: pam_unix(sudo:session): session opened for user root by root(uid=0)
May 18 15:33:53  systemd[1]: Starting The Apache HTTP Server...
-- Subject: Unit apache2.service has begun start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit apache2.service has begun starting up.
May 18 15:33:53  apachectl[31555]: Action 'start' failed.
May 18 15:33:53  apachectl[31555]: The Apache error log may have more information.
May 18 15:33:53  systemd[1]: apache2.service: Control process exited, code=exited status=1
May 18 15:33:53  systemd[1]: apache2.service: Failed with result 'exit-code'.
May 18 15:33:53  systemd[1]: Failed to start The Apache HTTP Server.
-- Subject: Unit apache2.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit apache2.service has failed.
--
-- The result is RESULT.
May 18 15:33:53  sudo[31549]: pam_unix(sudo:session): session closed for user root
May 18 15:33:55  kernel: [UFW BLOCK] IN=eth0 OUT= MAC=fa:52:65:0e:6a:71:fe:00:00:00:01:01:08:00 SRC=185.151.242.187 DST=167.99.179.159 LEN=40 TOS=0x00 PREC=0x00 TTL=240 ID=15380 PROTO=TCP SPT=21789 DPT=3377 WINDOW=1024 R
~
~
~
~
~
~
~
~
~
~
~
~
lines 1128-1150/1150 (END)
May 18 15:33:52  sshd[31542]: Failed password for invalid user bdt from 206.189.212.33 port 38420 ssh2
May 18 15:33:53  sudo[31549]:     root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/usr/sbin/service apache2 restart
May 18 15:33:53  sudo[31549]: pam_unix(sudo:session): session opened for user root by root(uid=0)
May 18 15:33:53  systemd[1]: Starting The Apache HTTP Server...
-- Subject: Unit apache2.service has begun start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit apache2.service has begun starting up.
May 18 15:33:53  apachectl[31555]: Action 'start' failed.
May 18 15:33:53  apachectl[31555]: The Apache error log may have more information.
May 18 15:33:53  systemd[1]: apache2.service: Control process exited, code=exited status=1
May 18 15:33:53  systemd[1]: apache2.service: Failed with result 'exit-code'.
May 18 15:33:53  systemd[1]: Failed to start The Apache HTTP Server.
-- Subject: Unit apache2.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit apache2.service has failed.
--
-- The result is RESULT.
May 18 15:33:53  sudo[31549]: pam_unix(sudo:session): session closed for user root
May 18 15:33:55  kernel: [UFW BLOCK] IN=eth0 OUT= MAC=fa:52:65:0e:6a:71:fe:00:00:00:01:01:08:00 SRC=185.151.242.187 DST=167.99.179.159 LEN=40 TOS=0x00 PREC=0x00 TTL=240 ID=15380 PROTO=TCP SPT=21789 DPT=3377 WINDOW=1024 RES=0x00 SYN URGP=0


当我尝试通过 sFTP 访问文件夹/usr/sbin/apachectl时，我们可以看到以下错误消息： Directory /usr/sbin/apache2ctl: no such file or directory

在文件/var/log/apache2/error.log中，我有 ：

[Mon May 18 15:33:53.451709 2020] [ssl:error] [pid 31566] AH02579: Init: Private key not found
[Mon May 18 15:33:53.451789 2020] [ssl:error] [pid 31566] SSL Library Error: error:0D0680A8:asn1 encoding routines:asn1_check_tlen:wrong tag
[Mon May 18 15:33:53.451800 2020] [ssl:error] [pid 31566] SSL Library Error: error:0D08303A:asn1 encoding routines:asn1_template_noexp_d2i:nested asn1 error
[Mon May 18 15:33:53.451807 2020] [ssl:error] [pid 31566] SSL Library Error: error:0D0680A8:asn1 encoding routines:asn1_check_tlen:wrong tag
[Mon May 18 15:33:53.451815 2020] [ssl:error] [pid 31566] SSL Library Error: error:0D07803A:asn1 encoding routines:asn1_item_embed_d2i:nested asn1 error (Type=RSAPrivateKey)
[Mon May 18 15:33:53.451823 2020] [ssl:error] [pid 31566] SSL Library Error: error:04093004:rsa routines:old_rsa_priv_decode:RSA lib
[Mon May 18 15:33:53.451830 2020] [ssl:error] [pid 31566] SSL Library Error: error:0D0680A8:asn1 encoding routines:asn1_check_tlen:wrong tag
[Mon May 18 15:33:53.451837 2020] [ssl:error] [pid 31566] SSL Library Error: error:0D07803A:asn1 encoding routines:asn1_item_embed_d2i:nested asn1 error (Type=PKCS8_PRIV_KEY_INFO)
[Mon May 18 15:33:53.451842 2020] [ssl:emerg] [pid 31566] AH02311: Fatal error initialising mod_ssl, exiting. See /var/log/apache2/error.log for more information
[Mon May 18 15:33:53.451846 2020] [ssl:emerg] [pid 31566] AH02564: Failed to configure encrypted (?) private key mydomain.com:443:0, check /root/certificate/mydomain.com.key
AH00016: Configuration Failed

任何帮助将非常感激。如果您需要检查其他内容，请告诉我您需要什么以及我如何获取这些信息。谢谢！

server ssl apache2 restart https
Martin Hope
svp
Asked: 2020-05-09 05:32:19 +0800 CST
  • 1

系统配置

Architecture:        x86_64
CPU op-mode(s):      32-bit, 64-bit
Byte Order:          Little Endian
CPU(s):              16
On-line CPU(s) list: 0-15
Thread(s) per core:  1
Core(s) per socket:  8
Socket(s):           2
NUMA node(s):        2
Vendor ID:           GenuineIntel
CPU family:          6
Model:               45
Model name:          Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz

我的系统每天都会在我不知情的情况下重新启动。我的系统的这种行为是否有任何解决方案。的输出last reboot如下：

reboot   system boot  5.3.0-51-generic Fri May  8 11:26   still running
reboot   system boot  5.3.0-51-generic Fri May  8 08:24   still running
reboot   system boot  5.3.0-51-generic Thu May  7 16:32   still running
reboot   system boot  5.3.0-51-generic Thu May  7 08:31   still running
reboot   system boot  5.3.0-51-generic Wed May  6 17:18   still running
reboot   system boot  5.3.0-51-generic Wed May  6 16:41   still running
reboot   system boot  5.3.0-51-generic Wed May  6 08:35   still running
reboot   system boot  5.3.0-51-generic Wed May  6 08:26   still running
reboot   system boot  5.3.0-51-generic Tue May  5 23:28   still running
reboot   system boot  5.3.0-51-generic Tue May  5 17:51   still running
reboot   system boot  5.3.0-51-generic Tue May  5 16:45   still running
reboot   system boot  5.3.0-51-generic Tue May  5 09:59   still running
reboot   system boot  5.3.0-51-generic Tue May  5 08:28   still running
reboot   system boot  5.3.0-51-generic Tue May  5 08:13   still running
reboot   system boot  5.3.0-51-generic Tue May  5 07:34   still running
reboot   system boot  5.3.0-51-generic Mon May  4 10:44   still running
reboot   system boot  5.3.0-51-generic Mon May  4 09:48   still running
reboot   system boot  5.3.0-51-generic Mon May  4 07:53   still running
reboot   system boot  5.3.0-51-generic Mon May  4 03:26   still running
reboot   system boot  5.3.0-51-generic Sun May  3 21:55   still running
reboot   system boot  5.3.0-51-generic Sun May  3 09:16   still running
reboot   system boot  5.3.0-51-generic Sat May  2 17:06   still running
reboot   system boot  5.3.0-51-generic Sat May  2 13:34   still running
reboot   system boot  5.3.0-51-generic Sat May  2 08:35   still running
reboot   system boot  5.3.0-51-generic Fri May  1 07:20   still running

wtmp begins Fri May  1 07:20:08 2020

命令的输出ls -al /usr/share/gnome-shell/extensions

total 64
drwxr-xr-x 16 root root 4096 Jan 23 12:26 .
drwxr-xr-x  6 root root 4096 Jan 14 11:30 ..
drwxr-xr-x  2 root root 4096 Jan 23 12:26 [email protected]
drwxr-xr-x  2 root root 4096 Jan 23 12:26 [email protected]
drwxr-xr-x  2 root root 4096 Jan 23 12:26 [email protected]
drwxr-xr-x  2 root root 4096 Jan 23 12:26 [email protected]
drwxr-xr-x  2 root root 4096 Jan 23 12:26 [email protected]
drwxr-xr-x  2 root root 4096 Jan 23 12:26 native-window-placement@gnome-shell-extensions.gcampax.github.com
drwxr-xr-x  2 root root 4096 Jan 23 12:26 [email protected]
drwxr-xr-x  2 root root 4096 Jan 23 12:26 screenshot-window-sizer@gnome-shell-extensions.gcampax.github.com
drwxr-xr-x  3 root root 4096 Aug  6  2019 [email protected]
drwxr-xr-x  3 root root 4096 Aug  6  2019 [email protected]
drwxr-xr-x  2 root root 4096 Jan 23 12:26 [email protected]
drwxr-xr-x  2 root root 4096 Jan 23 12:26 [email protected]
drwxr-xr-x  2 root root 4096 Jan 23 12:26 [email protected]
drwxr-xr-x  2 root root 4096 Jan 23 12:26 [email protected]

的输出ls -al ~/.local/share/gnome-shell/extensions No such file or directory

命令的输出ps auxc | grep -i therm

root       250  0.0  0.0      0     0 ?        I<   May08   0:00 acpi_thermal_pm
reboot restart 18.04
Martin Hope
BenKoshy
Asked: 2020-03-06 22:00:02 +0800 CST
  • 2

在 3-4 次重新启动尝试的空间中，它重新启动了大约 3-4 次。

这是双启动，我 85% 的时间都在使用 Ubuntu。每次我在加载 ubuntu 时（在我输入用户名和密码之后）到达同一点时，它都会重新启动。在其他时候，即使没有启动，它也会随机重启，但这种情况很少见（每周一次左右）。这开始成为一个非常令人担忧的问题。正在寻求更多知识渊博的人的帮助。担心是硬件问题！哎呀！

Ubuntu 18.04.3 LTS
31.3 GiB
Intel® Core™ i7-8700 CPU @ 3.20GHz × 12 
NV134
3.28.2
64-bit
210.5 GB

tail -f /var/log/syslog
Mar  6 16:36:10 koshy-System-Product-Name colord[1352]: failed to get session [pid 4355]: No data available
Mar  6 16:36:10 koshy-System-Product-Name rsyslogd:  [origin software="rsyslogd" swVersion="8.32.0" x-pid="1299" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
Mar  6 16:36:34 koshy-System-Product-Name rtkit-daemon[1652]: Supervising 7 threads of 4 processes of 1 users.
Mar  6 16:36:34 koshy-System-Product-Name rtkit-daemon[1652]: Supervising 7 threads of 4 processes of 1 users.
Mar  6 16:37:13 koshy-System-Product-Name anacron[1268]: Job `cron.daily' terminated
Mar  6 16:37:13 koshy-System-Product-Name anacron[1268]: Normal exit (1 job run)
Mar  6 16:37:20 koshy-System-Product-Name rtkit-daemon[1652]: Supervising 7 threads of 4 processes of 1 users.
Mar  6 16:37:55 koshy-System-Product-Name rtkit-daemon[1652]: message repeated 7 times: [ Supervising 7 threads of 4 processes of 1 users.]
Mar  6 16:37:55 koshy-System-Product-Name rtkit-daemon[1652]: Successfully made thread 4581 of process 2784 (n/a) owned by '1000' RT at priority 10.
Mar  6 16:37:55 koshy-System-Product-Name rtkit-daemon[1652]: Supervising 8 threads of 5 processes of 1 users.



koshy@koshy-System-Product-Name:~$ last reboot
reboot   system boot  4.15.0-88-generi Sat Mar  7 03:31   still running
reboot   system boot  4.15.0-88-generi Fri Mar  6 08:07 - 14:49  (06:42)
reboot   system boot  4.15.0-88-generi Fri Mar  6 00:21 - 16:32  (-7:48)
reboot   system boot  4.15.0-88-generi Thu Mar  5 09:01 - 11:32  (02:31)
reboot   system boot  4.15.0-88-generi Wed Mar  4 18:19 - 18:19  (00:00)
reboot   system boot  4.15.0-88-generi Wed Mar  4 17:27 - 18:19  (00:52)
reboot   system boot  4.15.0-88-generi Wed Mar  4 17:12 - 17:25  (00:12)
reboot   system boot  4.15.0-88-generi Wed Mar  4 09:43 - 17:25  (07:41)
reboot   system boot  4.15.0-88-generi Tue Mar  3 11:03 - 17:25 (1+06:21)

wtmp begins Mon Mar  2 08:30:26 2020

这是我的系统规格：https ://gist.github.com/BKSpureon/3314c608d4f73be7e3a596f4413e80cb

如果您需要更多日志，请告诉我，我会提供。

谢谢！

boot hardware restart
Martin Hope
Kirk Johnston
Asked: 2019-11-11 22:16:51 +0800 CST
  • 0

我有一个站点在我的 Ubuntu 18.04.3 服务器上运行了大约 5 个月，没有出现任何问题。

我最近将另外两个小型站点移至该服务器。

突然，我醒来看到所有 3 个站点的停机时间报告。

问题是建立数据库连接时出错。

运行以下修复它...

sudo /etc/init.d/mysql start

内的原始值

/etc/systemd/system/multi-user.target.wants/mysqld.service

曾是

Restart=on-failure

但读完这篇文章后，我把它改成了

Restart=always

我在 3 天前进行了此更改，但今天我已经意识到同样的问题。我不得不跑...

sudo /etc/init.d/mysql start

尽管

/etc/systemd/system/multi-user.target.wants/mysqld.service

被设置为

Restart=always

我遇到了这个类似的问题，但答案是负1。

如果有人可以提供一些进一步的建议，将不胜感激。

服务文件的内容...

# MySQL systemd service file

[Unit]
Description=MySQL Community Server
After=network.target

[Install]
WantedBy=multi-user.target

[Service]
Type=forking
User=mysql
Group=mysql
PIDFile=/run/mysqld/mysqld.pid
PermissionsStartOnly=true
ExecStartPre=/usr/share/mysql/mysql-systemd-start pre
ExecStart=/usr/sbin/mysqld --daemonize --pid-file=/run/mysqld/mysqld.pid
TimeoutSec=600
Restart=always
RuntimeDirectory=mysqld
RuntimeDirectoryMode=755
LimitNOFILE=5000

在此处查看 journalctl 文件。

mysql restart
Martin Hope
Jared
Asked: 2018-11-25 12:31:19 +0800 CST
  • 2

我在不到一个月前安装了 Ubuntu，从那时起我就一直在玩我能做的事情，所以我可能在这个过程中弄坏了一些东西。

最近我重新启动了我的电脑（Matebook x Pro），它卡在一个循环中，键盘亮起，风扇旋转一秒钟，带有华为标志的黑屏出现，然后一切都立即关闭。然后一秒钟后，它再次重复。

我尝试关闭它，等待，然后再次打开它，但循环仍在继续。

我想知道是否有任何启动修复快捷方式可以用来再次正常启动。

我不是双启动。Ubuntu是计算机上唯一的操作系统。电脑是新的；我是一个月前买的，所以我怀疑是不是硬件故障。我想我可以通过调出某种命令行或使用某种快捷方式来解决这个问题。

我不确定是什么导致了这个问题。我可能不小心为 Ubuntu 16 安装了一些软件包，这可能会破坏某些东西？我通过终端安装了不同的东西，指令说要重新启动计算机，我现在就在这里。我不记得我到底想安装什么，因为我玩过很多东西，但我认为这不会影响启动指令，因为它们是只读的？

当我点击评论中的链接时，这是我得到的：

BIOS/UEFI 设置

ctrl++组合将我带到 InsydeH20 设置实用程序alt。f2

编辑：我认为这是因为我的 BIOS 已过时。我的版本是 something.17，但有 .18 版本可用。我已将 zip 文件下载到我的闪存驱动器上，但计算机看不到它

boot restart 18.04