计算引擎 | 无法启动LSB：宝藏数据收集器

Question

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

\n\n

Wordpress 发布了新的更新 (5.4)，我想更新它。为此，我需要升级虚拟机，因为新的 WordPress 版本安装失败，甚至无法启动。

\n\n

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

\n\n

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

\n\n

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

\n\n

Building dependency tree       \nReading state information... Done\nCalculating upgrade... Done\n0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.\n1 not fully installed or removed.\nAfter this operation, 0 B of additional disk space will be used.\nSetting up google-fluentd (1.6.33-1) ...\nConffile /etc/google-fluentd/google-fluentd.conf has been modified. Remain untouched.\nJob for google-fluentd.service failed because the control process exited with error code.\nSee "systemctl status google-fluentd.service" and "journalctl -xe" for details.\ninvoke-rc.d: initscript google-fluentd, action "start" failed.\n\xe2\x97\x8f google-fluentd.service - LSB: data collector for Treasure Data\n  Loaded: loaded (/etc/init.d/google-fluentd; generated; vendor preset: enabled)\n  Active: failed (Result: exit-code) since Sun 2020-04-19 20:15:44 UTC; 20ms ago\n    Docs: man:systemd-sysv-generator(8)\n Process: 20187 ExecStart=/etc/init.d/google-fluentd start (code=exited, status=1/FAILURE)\nApr 19 20:15:44 agentur-m-wp-vm systemd[1]: Starting LSB: data collector for Treasure Data...\nApr 19 20:15:44 agentur-m-wp-vm google-fluentd[20187]: Starting google-fluentd 1.6.33: Disabled via metadata \xe2\x80\xa6ing).\nApr 19 20:15:44 agentur-m-wp-vm google-fluentd[20187]: google-fluentd ... failed!\nApr 19 20:15:44 agentur-m-wp-vm systemd[1]: google-fluentd.service: Control process exited, code=exited status=1\nApr 19 20:15:44 agentur-m-wp-vm systemd[1]: Failed to start LSB: data collector for Treasure Data.\nApr 19 20:15:44 agentur-m-wp-vm systemd[1]: google-fluentd.service: Unit entered failed state.\nApr 19 20:15:44 agentur-m-wp-vm systemd[1]: google-fluentd.service: Failed with result \'exit-code\'.\nHint: Some lines were ellipsized, use -l to show in full.\ndpkg: error processing package google-fluentd (--configure):\nsubprocess installed post-installation script returned error exit status 1\nErrors were encountered while processing:\ngoogle-fluentd\nE: Sub-process /usr/bin/dpkg returned an error code (1)\n

\n\n

我真的没有 SSH 经验，所以如果你能帮助我解决这个问题，我将是地球上最幸福的人。

\n\n

太感谢了。

\n\n

亲切的问候\nVazanity。

\n\n

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

\n\n

这就是我得到的：

\n\n

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

\n\n

更新：\n现在当我这样做时sudo apt update

\n\n

我得到以下输出：

\n\n

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

\n\n

sudo apt upgrade一切顺利，所有软件包均已安装/更新。

\n\n

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

\n\n

而已。

\n\n

新更新

\n\n

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

\n\n

（好像一切都升级了）

\n\n

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

\n\n

Reading package lists... Done\nBuilding dependency tree       \nReading state information... Done\nCalculating upgrade... Done\nThe following packages were automatically installed and are no longer required:\n  sgml-base xml-core\nUse \'sudo apt autoremove\' to remove them.\n0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.\n

\n\n

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

\n\n

我究竟做错了什么... ：（

\n

Answer 1

您的日志记录代理 有问题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

查看文档对代理进行故障排除：

如果重新启动失败，并且日志输出显示“通过元数据禁用”，则您可能正在运行来自 Google Cloud Marketplace 的映像，其中默认情况下禁用日志记录代理。这是由google-logging-enable实例元数据键（值为 0）控制的。

要解决您的问题：

• 重新启动代理：

  sudo service google-fluentd status
  

  并检查日志是否有相同的错误Disabled via metadata

• 按照以下说明重新启用代理：

  要重新启用代理，请删除该键或将值设置为 1（请参阅设置实例元数据）。

• 重新启动并再次检查代理的状态：

  sudo service google-fluentd restart
  sudo service google-fluentd status
  

  如果没有看到错误，则可以sudo apt upgrade -y再次运行。

不要忘记在任何更改之前创建快照/备份以保护您的数据。

编辑看看文档 更新WordPress，如果没有帮助，请尝试 手动更新。