Access Being denied when setting up clusterhat

[jcl...@umbc.edu]

In reference to https://groups.google.com/forum/#!topic/clusterhat/vwiVEcjz3L0 :

When I try to run the echo commands when setting up the Pi Zero's, I get the following errors:

debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied

debconf: DbDriver "config" could not write /var/cache/debconf/config.dat-new: Permission denied

** passwords.dat says that the file is unreadable, and config.dat-new was not even created at this point. (Do these mean I cannot access ../debconf directory at all?)

-------------------------------------------------------------------------------------------------------------------------------------------------------------------

Changing permissions to the directory gave me a different error, so I switched them back to avoid conflict down the road.

I am currently using and SD card setup, running Raspbian Stretch with Desktop/Lite.

[jcl...@umbc.edu]

Currently Using the Pi Zero WIRELESS!

[Chris Burton]

Hi, 

When I try to run the echo commands when setting up the Pi Zero's, I get the following errors:

debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied

debconf: DbDriver "config" could not write /var/cache/debconf/config.dat-new: Permission denied

** passwords.dat says that the file is unreadable, and config.dat-new was not even created at this point. (Do these mean I cannot access ../debconf directory at all?)

See my reply from a couple of days ago. You need to run those commands as root - https://groups.google.com/d/msg/clusterhat/vwiVEcjz3L0/RTlQ8s5LAQAJ 

Chris.

[jcl...@umbc.edu]

Chris,

I have already tried that and get the same errors. I have also tried reinstalling the directory Incase there were corrupt files, but am getting the same issues nonetheless.

[Chris Burton]

Hi, 

I have already tried that and get the same errors. I have also tried reinstalling the directory Incase there were corrupt files, but am getting the same issues nonetheless.

If the root user is unable open the file then something really doesn't sound right.

I would advise starting with a fresh images and document it fully - so which image you're using on which Pi, physical setup, all changes/commands you run on each Pi so if you have the same problem again I have some chance of replicating it.

Chris.