crontab in V2

crontab no longer seems to be available in Volumio V2.
I’ve looked to see if it was still blocked in /var/www/command/orion_optimize.sh but this path does not exist in V2.

Is there any way to implement it ?

Cron is simply not installed in VOlumio2. But you can install it without problems!

apt-get update && apt-get install -y cron

OK, thanks for that confirmation.

I’ve tried that command both with sudo at the start and without and I get the following errors:

[code]volumio@Volumio:~$ sudo apt-get update && apt-get install -y cron
Err http://archive.raspbian.org jessie InRelease

Err http://archive.raspbian.org jessie Release.gpg
Temporary failure resolving ‘archive.raspbian.org
Reading package lists… Done
W: Failed to fetch http://archive.raspbian.org/raspbian/dists/jessie/InRelease

W: Failed to fetch http://archive.raspbian.org/raspbian/dists/jessie/Release.gpg Temporary failure resolving ‘archive.raspbian.org

W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists… Done
Building dependency tree
Reading state information… Done
Package cron is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package ‘cron’ has no installation candidate
volumio@Volumio:~$ crontab -l
-bash: crontab: command not found
volumio@Volumio:~$ apt-get update && apt-get install -y cron
Err http://archive.raspbian.org jessie InRelease

Err http://archive.raspbian.org jessie Release.gpg
Temporary failure resolving ‘archive.raspbian.org
Reading package lists… Done
W: Failed to fetch http://archive.raspbian.org/raspbian/dists/jessie/InRelease

W: Failed to fetch http://archive.raspbian.org/raspbian/dists/jessie/Release.gpg Temporary failure resolving ‘archive.raspbian.org

W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists… Done
Building dependency tree
Reading state information… Done
Package cron is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package ‘cron’ has no installation candidate
[/code]

I can confirm we are having the same issue installing cron – see below

root@musiccab2:/home/sheridanpoint# sudo apt-get install cron Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: libpam-systemd : Depends: systemd (= 215-17+deb8u5) but 215-17+deb8u4 is to be installed systemd : Depends: libsystemd0 (= 215-17+deb8u4) but 215-17+deb8u5 is to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). root@musiccab2:/home/sheridanpoint# sudo apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following extra packages will be installed: systemd systemd-sysv Suggested packages: systemd-ui The following packages will be upgraded: systemd systemd-sysv 2 upgraded, 0 newly installed, 0 to remove and 45 not upgraded. 2 not fully installed or removed. Need to get 0 B/2,247 kB of archives. After this operation, 1,024 B of additional disk space will be used. Do you want to continue? [Y/n] y debconf: delaying package configuration, since apt-utils is not installed dpkg: warning: files list file for package 'isc-dhcp-client' missing; assuming package has no files currently installed (Reading database ... 18040 files and directories currently installed.) Preparing to unpack .../systemd_215-17+deb8u5_armhf.deb ... Unpacking systemd (215-17+deb8u5) over (215-17+deb8u4) ... dpkg: error processing archive /var/cache/apt/archives/systemd_215-17+deb8u5_armhf.deb (--unpack): trying to overwrite '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service', which is also in package systemd-shim 9-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) addgroup: The group `systemd-journal' already exists as a system group. Exiting. Processing triggers for dbus (1.8.20-0+deb8u1) ... Errors were encountered while processing: /var/cache/apt/archives/systemd_215-17+deb8u5_armhf.deb E: Sub-process /usr/bin/dpkg returned an error code (1)

Volumio 2.0.39
sudo apt-get install cron = no problem…

volumio@volumio-hifiberry:~$ crontab -l no crontab for volumio

We are running 2.0.31 – checking for updates to get to 2.0.39 does not work, it indicates we are on the latest version.

volumio.github.io/docs/User_Man … dates.html
See the beta releases part :wink:

Thanks! Is the issue with packages a known issue in 2.0.31? Was unable to find a bug report about it in github

Spoke too soon! Update to 2.040 and getting the same error :frowning:

root@musiccab2:/home/sheridanpoint# sudo apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following extra packages will be installed: systemd systemd-sysv Suggested packages: systemd-ui The following packages will be upgraded: systemd systemd-sysv 2 upgraded, 0 newly installed, 0 to remove and 45 not upgraded. 2 not fully installed or removed. Need to get 0 B/2,247 kB of archives. After this operation, 1,024 B of additional disk space will be used. Do you want to continue? [Y/n] y debconf: delaying package configuration, since apt-utils is not installed dpkg: warning: files list file for package 'isc-dhcp-client' missing; assuming package has no files currently installed (Reading database ... 18040 files and directories currently installed.) Preparing to unpack .../systemd_215-17+deb8u5_armhf.deb ... Unpacking systemd (215-17+deb8u5) over (215-17+deb8u4) ... dpkg: error processing archive /var/cache/apt/archives/systemd_215-17+deb8u5_armhf.deb (--unpack): trying to overwrite '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service', which is also in package systemd-shim 9-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) addgroup: The group `systemd-journal' already exists as a system group. Exiting. Processing triggers for dbus (1.8.20-0+deb8u1) ... Errors were encountered while processing: /var/cache/apt/archives/systemd_215-17+deb8u5_armhf.deb E: Sub-process /usr/bin/dpkg returned an error code (1)

Hi All,

Any ideas?

Forgot to mention that I’m running the latest stable version 2.030/2.031 (I can’t remember)

Is the inability to do a package install also likely to prevent me from installing xlstproc (as per my other thread: issues-installing-mashpodder-crontab-and-xsltproc-missing-t5329.html)

I figured it out yesterday, did you by any chance change the default volumio password?

If so, change it back… changing the password breaks things. A lot of things.

Nope, I only installed it recently and haven’t tinkered around with anything much. Username/Password is still volumio/volumio

Anything?

I would much rather avoid reinstalling especially when it seems other people had issues even after reinstalling.

happy new year !!!
sorry to start with but same error on 2.041
trying to install “hdparm”

volumio@volumio:/etc$ sudo apt-get update && apt-get install -y hdparm          Err http://archive.raspbian.org jessie InRelease

Err http://archive.raspbian.org jessie Release.gpg
  Temporary failure resolving 'archive.raspbian.org'
Reading package lists... Done
W: Failed to fetch http://archive.raspbian.org/raspbian/dists/jessie/InRelease
W: Failed to fetch http://archive.raspbian.org/raspbian/dists/jessie/Release.gpg  Temporary failure resolving 'archive.raspbian.org'

that is not a Volumio problem, you try to read from the raspbian site and have no connection.
Either you have network problems or the raspbian site was not available.

I’ve figured out why I wasn’t able to install crontab and likely why other people can’t do any package updates.

In the system configuration via the Volumio UI I had set DHCP to be manual, but I hadn’t set the gateway (it was set to 0.0.0.0) so once I set it to 192.168.0.1 (the IP of my router) it worked a treat!

Solved it myself by fresh install. pain in the backside but it worked.