计算引擎 | LSB 启动失败：Treasure Data 的数据采集器答案

【问题标题】：Compute engine | Failed to start LSB: data collector for treasure Data计算引擎 | LSB 启动失败：Treasure Data 的数据采集器
【发布时间】：2021-08-15 21:32:14
【问题描述】：

我在 google 的计算引擎上设置了一个带有 wordpress 的新虚拟机。现在我面临以下问题：

Wordpress 发布了一个新的更新 (5.4)，我想更新它。为此，我需要对 vm 进行升级，因为安装新的 wordpress 版本失败，甚至无法启动。

所以现在我解决这个问题的想法是，也许我需要更新 php 版本或整个 vm。

我尝试这样做，但现在我收到以下错误：无法启动 LSB：宝藏数据的数据收集器。

这是我使用命令sudo apt upgrade -y时得到的结果

Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up google-fluentd (1.6.33-1) ...
Conffile /etc/google-fluentd/google-fluentd.conf has been modified. Remain untouched.
Job for google-fluentd.service failed because the control process exited with error code.
See "systemctl status google-fluentd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript google-fluentd, action "start" failed.
● google-fluentd.service - LSB: data collector for Treasure Data
  Loaded: loaded (/etc/init.d/google-fluentd; generated; vendor preset: enabled)
  Active: failed (Result: exit-code) since Sun 2020-04-19 20:15:44 UTC; 20ms ago
    Docs: man:systemd-sysv-generator(8)
 Process: 20187 ExecStart=/etc/init.d/google-fluentd start (code=exited, status=1/FAILURE)
Apr 19 20:15:44 agentur-m-wp-vm systemd[1]: Starting LSB: data collector for Treasure Data...
Apr 19 20:15:44 agentur-m-wp-vm google-fluentd[20187]: Starting google-fluentd 1.6.33: Disabled via metadata …ing).
Apr 19 20:15:44 agentur-m-wp-vm google-fluentd[20187]: google-fluentd ... failed!
Apr 19 20:15:44 agentur-m-wp-vm systemd[1]: google-fluentd.service: Control process exited, code=exited status=1
Apr 19 20:15:44 agentur-m-wp-vm systemd[1]: Failed to start LSB: data collector for Treasure Data.
Apr 19 20:15:44 agentur-m-wp-vm systemd[1]: google-fluentd.service: Unit entered failed state.
Apr 19 20:15:44 agentur-m-wp-vm systemd[1]: google-fluentd.service: Failed with result 'exit-code'.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package google-fluentd (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
google-fluentd
E: Sub-process /usr/bin/dpkg returned an error code (1)

我真的没有使用 SSH 的经验，所以如果你能帮助我解决这个问题，我会是地球上最快乐的人。

非常感谢。

亲切的问候虚无。

编辑：如果这对您有帮助，我使用此命令获取详细的错误消息： journalctl -xe

这就是我得到的：

Apr 19 20:29:23 agentur-m-wp-vm systemd[1]: apt-daily.timer: Adding 13min 21.259584s random time.
Apr 19 20:29:23 agentur-m-wp-vm systemd[1]: certbot.timer: Adding 10h 18min 6.712498s random time.
Apr 19 20:29:23 agentur-m-wp-vm systemd[1]: Starting Daily apt download activities...
-- Subject: Unit apt-daily.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit apt-daily.service has begun starting up.
Apr 19 20:29:23 agentur-m-wp-vm systemd[1]: Reloading.
Apr 19 20:29:23 agentur-m-wp-vm systemd[1]: certbot.timer: Adding 2h 11min 1.812555s random time.
Apr 19 20:29:23 agentur-m-wp-vm systemd[1]: certbot.timer: Adding 5h 3min 3.480078s random time.
Apr 19 20:29:23 agentur-m-wp-vm systemd[1]: apt-daily-upgrade.timer: Adding 55min 49.753301s random time.
Apr 19 20:29:23 agentur-m-wp-vm systemd[1]: Started Daily apt download activities.
-- Subject: Unit apt-daily.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit apt-daily.service has finished starting up.
-- 
-- The start-up result is done.
Apr 19 20:29:23 agentur-m-wp-vm systemd[1]: apt-daily.timer: Adding 3h 27min 38.579330s random time.
Apr 19 20:29:23 agentur-m-wp-vm systemd[1]: apt-daily.timer: Adding 7h 2min 37.043471s random time.
Apr 19 20:29:23 agentur-m-wp-vm systemd[1]: Starting LSB: data collector for Treasure Data...
-- Subject: Unit google-fluentd.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit google-fluentd.service has begun starting up.
Apr 19 20:29:23 agentur-m-wp-vm google-fluentd[20542]: Starting google-fluentd 1.6.33: Disabled via metadata ... (w
Apr 19 20:29:23 agentur-m-wp-vm google-fluentd[20542]: google-fluentd ... failed!
Apr 19 20:29:23 agentur-m-wp-vm systemd[1]: google-fluentd.service: Control process exited, code=exited status=1
Apr 19 20:29:23 agentur-m-wp-vm systemd[1]: Failed to start LSB: data collector for Treasure Data.
-- Subject: Unit google-fluentd.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit google-fluentd.service has failed.
-- 
-- The result is failed.
Apr 19 20:29:23 agentur-m-wp-vm systemd[1]: google-fluentd.service: Unit entered failed state.
Apr 19 20:29:23 agentur-m-wp-vm systemd[1]: google-fluentd.service: Failed with result 'exit-code'.
Apr 19 20:29:23 agentur-m-wp-vm sudo[20460]: pam_unix(sudo:session): session closed for user root
lines 1308-1349/1349 (END)

更新：现在当我做sudo apt update

我得到以下输出：

Hit:1 http://security.debian.org stretch/updates InRelease
Ign:2 http://deb.debian.org/debian stretch InRelease                
Hit:3 http://deb.debian.org/debian stretch-updates InRelease        
Hit:4 http://repo.mysql.com/apt/debian stretch InRelease            
Hit:5 http://deb.debian.org/debian stretch-backports InRelease           
Hit:6 http://packages.cloud.google.com/apt google-cloud-logging-wheezy InRelease
Hit:7 http://deb.debian.org/debian stretch Release                       
Hit:8 http://packages.cloud.google.com/apt google-cloud-monitoring-stretch InRelease
Hit:9 http://packages.cloud.google.com/apt cloud-sdk-stretch InRelease
Hit:10 http://packages.cloud.google.com/apt google-compute-engine-stretch-stable InRelease
Hit:11 http://packages.cloud.google.com/apt google-cloud-packages-archive-keyring-stretch InRelease
Get:12 https://packages.sury.org/php stretch InRelease [6,760 B]
Fetched 6,760 B in 1s (6,311 B/s)
Reading package lists... Done
Building dependency tree       
Reading state information... Done
13 packages can be upgraded. Run 'apt list --upgradable' to see them.

sudo apt upgrade 顺利，所有包都已安装/更新。

现在我尝试通过后端再次更新 wordpress，它仍然显示“下载失败”、“出现问题”。

仅此而已。

新更新

我现在正在跑步sudo apt list --upgradable 并得到以下输出：Listing Done

（好像都升级了）

为了确保我现在正在运行下一个命令sudo apt upgrade -y

Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  sgml-base xml-core
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

嗯。我的假设是正确的.. 但仍然无法在后端更新 wordpress..

我做错了什么... :(

【问题讨论】：

标签： php wordpress ssh google-cloud-platform google-compute-engine

【解决方案1】：

您对logging agent google-fluentd 有疑问：

Apr 19 20:29:23 agentur-m-wp-vm systemd[1]: Starting LSB: data collector for Treasure Data

你也可以在日志中看到它的原因：

Apr 19 20:29:23 agentur-m-wp-vm google-fluentd[20542]: Starting google-fluentd 1.6.33: Disabled via metadata

查看文档Troubleshooting the Agent：

如果重启失败，并且日志输出显示“Disabled via 元数据”，您可能正在运行来自 Google Cloud 的图像市场，默认情况下禁用 Logging 代理。这是由google-logging-enable 实例元数据键控制（使用值 0)。

解决您的问题：

重启代理：
```
sudo service google-fluentd status
```
如果你有同样的错误，请检查日志Disabled via metadata
通过关注instructions重新启用代理：

要重新启用代理，请删除该密钥或设置值为 1（请参阅Setting instance metadata）。
重新启动并再次检查代理的状态：
```
sudo service google-fluentd restart
sudo service google-fluentd status
```
如果您没有看到任何错误，您可以再次运行sudo apt upgrade -y。

不要忘记创建snapshot/backup 以在任何更改之前保护您的数据。

编辑查看文档Updating WordPress，如果没有任何帮助，请尝试Manual Update。

【讨论】：

感谢您的帮助！看来我不再有错误了。我刚刚进行了升级，但似乎有些奇怪？它说 1 没有完全安装。这是为什么呢？
它似乎有效，但仍然无法更新 wordpress。 VM 说有 13 个包更新可用。有没有办法一起更新这些？
请使用命令sudo apt update 和sudo apt upgrade 的输出更新您的问题。也请分享您升级 WordPress 的步骤和错误消息。
嗨，Serhii，我按照您的步骤操作并更新了我上面的问题。
查看消息“13 个软件包可以升级”，首先您应该运行“sudo apt list --upgradable”，然后运行“sudo apt upgrade -y”。请使用这些命令的完整输出更新您的问题。

【解决方案2】：

我遇到了同样的问题。您应该使用以下命令停止并卸载 google-fluentd：

sudo service google-fluentd stop && sudo apt-get remove google-fluentd google-fluentd-catch-all-config

【讨论】：