时间戳

首页 > 解决方案 > 计算引擎 | LSB 启动失败：Treasure Data 的数据采集器

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

问题描述

我在谷歌的计算引擎上用 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 的经验，所以如果你能帮助我解决这个问题，我将成为地球上最快乐的人。

太感谢了。

亲切的问候Vazanity。

编辑：如果这对您有帮助，我使用此命令获取详细的错误消息： 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..

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

标签： phpwordpresssshgoogle-cloud-platformgoogle-compute-engine

解决方案

您对日志记录代理 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

查看文档故障排除代理：

如果重启失败，并且日志输出显示“Disabled via metadata”，您可能正在运行来自 Google Cloud Marketplace 的映像，其中 Logging 代理默认处于禁用状态。这由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，如果没有任何帮助，请尝试 手动更新。

推荐阅读