title: Compute engine | Failed to start LSB: data collector for treasure Data
body: <p>I've set up a new virtual machine with wordpress on google's compute engine.
  Now I'm facing the following problem:</p>
  
  <p>Wordpress has released a new update (5.4) and I want update it. To do that, I need to do an upgrade of the vm because the installation of the new wordpress version fails and can't even start.</p>
  
  <p>So now my thoughts on solving this problem were, maybe I need to update the php version or the whole vm.</p>
  
  <p>I tried to do it but now i'm getting the following error: Failed to start LSB: data colector for treasure Data.</p>
  
  <p>This is what i've got when I used the command <code>sudo apt upgrade -y</code></p>
  
  <pre><code>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)
  </code></pre>
  
  <p>I'm really not experienced with SSH so I would be the happiest human on earth if you could help me with this issue.</p>
  
  <p>Thank you so much.</p>
  
  <p>Kind regards
  Vazanity.</p>
  
  <p>EDIT:
  If this helps you I used this command to get a detailed error message:
  <code>journalctl -xe</code></p>
  
  <p>And this is what I got:</p>
  
  <pre><code>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)
  </code></pre>
  
  <p>UPDATE:
  Now when I do <code>sudo apt update</code></p>
  
  <p>I get the following output:</p>
  
  <pre><code>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.
  </code></pre>
  
  <p><code>sudo apt upgrade</code> went well, all packages have been installed/updated.</p>
  
  <p>Now I tried to update wordpress again via backend and it still says "download failed" , "something went wrong".</p>
  
  <p>Nothing more.</p>
  
  <p><strong>NEW UPDATE</strong></p>
  
  <p>I am running now <code>sudo apt list --upgradable</code>
  and get the following output: Listing Done</p>
  
  <p>(It seems like everything has been upgraded)</p>
  
  <p>To be sure I'm running now the next command <code>sudo apt upgrade -y</code></p>
  
  <pre><code>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.
  </code></pre>
  
  <p>Well. My assumption was right.. but still can't update wordpress in the backend..</p>
  
  <p>What am I doing wrong... :(</p>