starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

Wallos: /var/log/cron does not exist #62

New Issue
Closed
opened 2026-02-04 16:24:34 +03:00 by OVERLORD · 11 comments
OVERLORD commented 2026-02-04 16:24:34 +03:00
Owner
Copy Link

Originally created by @burgerga on GitHub (Nov 17, 2024).

Originally assigned to: @MickLesk on GitHub.

Please verify that you have read and understood the guidelines.

yes

A clear and concise description of the issue.

/var/mail/root is full with emails like:

Subject: Cron <root@wallos> php /opt/wallos/endpoints/cronjobs/sendverificationemails.php >> /var/log/cron/sendverificationemail.log 2>&1
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=root>
Message-Id: <20241117190601.8D49820965@wallos.localdomain>
Date: Sun, 17 Nov 2024 19:06:01 +0000 (UTC)

/bin/sh: 1: cannot create /var/log/cron/sendverificationemail.log: Directory nonexistent

caused by 61d2e0d599/install/wallos-install.sh (L61-L72)

I think you could redirect the output to logger, which also avoids filling up the disk (see https://serverfault.com/a/434902/178440)

What settings are you currently utilizing?

Default Settings

Which Linux distribution are you employing?

Debian 12

If relevant, including screenshots or a code block can be helpful in clarifying the issue.

No response

Please provide detailed steps to reproduce the issue.

No response

Originally created by @burgerga on GitHub (Nov 17, 2024). Originally assigned to: @MickLesk on GitHub. ### Please verify that you have read and understood the guidelines. yes ### A clear and concise description of the issue. `/var/mail/root` is full with emails like: ```bash Subject: Cron <root@wallos> php /opt/wallos/endpoints/cronjobs/sendverificationemails.php >> /var/log/cron/sendverificationemail.log 2>&1 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit X-Cron-Env: <SHELL=/bin/sh> X-Cron-Env: <HOME=/root> X-Cron-Env: <PATH=/usr/bin:/bin> X-Cron-Env: <LOGNAME=root> Message-Id: <20241117190601.8D49820965@wallos.localdomain> Date: Sun, 17 Nov 2024 19:06:01 +0000 (UTC) /bin/sh: 1: cannot create /var/log/cron/sendverificationemail.log: Directory nonexistent ``` caused by https://github.com/community-scripts/ProxmoxVE/blob/61d2e0d599b88a3273198c6b747285049636b926/install/wallos-install.sh#L61-L72 I think you could redirect the output to `logger`, which also avoids filling up the disk (see https://serverfault.com/a/434902/178440) ### What settings are you currently utilizing? Default Settings ### Which Linux distribution are you employing? Debian 12 ### If relevant, including screenshots or a code block can be helpful in clarifying the issue. _No response_ ### Please provide detailed steps to reproduce the issue. _No response_
OVERLORD added the bug label 2026-02-04 16:24:34 +03:00
OVERLORD commented 2026-02-04 16:24:40 +03:00
Author
Owner
Copy Link

@burgerga commented on GitHub (Nov 17, 2024):

I see this was in the official instructions, so I opened an issue at wallos as well

@burgerga commented on GitHub (Nov 17, 2024): I see this was in the official instructions, so I opened an issue at wallos as well
OVERLORD commented 2026-02-04 16:24:48 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 17, 2024):

I fix it tomorrow with the other Wallos issue

@MickLesk commented on GitHub (Nov 17, 2024): I fix it tomorrow with the other Wallos issue
OVERLORD commented 2026-02-04 16:24:54 +03:00
Author
Owner
Copy Link

@Aloe-recite commented on GitHub (Nov 18, 2024):

@MickLesk how shall we proceed to benefit of the updated script? Shall we run it again from PVE shell or simply use the "update" function in the LXC? Or shall we nuke the existing container and start over to clean it from leftovers?
Thanks!

@Aloe-recite commented on GitHub (Nov 18, 2024): @MickLesk how shall we proceed to benefit of the updated script? Shall we run it again from PVE shell or simply use the "update" function in the LXC? Or shall we nuke the existing container and start over to clean it from leftovers? Thanks!
OVERLORD commented 2026-02-04 16:24:59 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 18, 2024):

Update is enough. If there is no Update available Just enter: mkdir -p /var/log/cron

@MickLesk commented on GitHub (Nov 18, 2024): Update is enough. If there is no Update available Just enter: mkdir -p /var/log/cron
OVERLORD commented 2026-02-04 16:25:06 +03:00
Author
Owner
Copy Link

@Aloe-recite commented on GitHub (Nov 18, 2024):

I run the "update" (from 2.38.0 to 2.38.1) command but am getting errors:

 /mv: cannot move '/opt/wallos/images/uploads' to '/opt/images/uploads': No such file or directory

[ERROR] in line 67: exit code 0: while executing command mv /opt/wallos/images/uploads /opt/images/uploads

I manually created the missing dir but then:

|mv: cannot stat '/opt/wallos/db/wallos.db': No such file or directory

[ERROR] in line 66: exit code 0: while executing command mv /opt/wallos/db/wallos.db /opt/wallos.db
@Aloe-recite commented on GitHub (Nov 18, 2024): I run the "update" (from 2.38.0 to 2.38.1) command but am getting errors: ``` /mv: cannot move '/opt/wallos/images/uploads' to '/opt/images/uploads': No such file or directory [ERROR] in line 67: exit code 0: while executing command mv /opt/wallos/images/uploads /opt/images/uploads ``` I manually created the missing dir but then: ``` |mv: cannot stat '/opt/wallos/db/wallos.db': No such file or directory [ERROR] in line 66: exit code 0: while executing command mv /opt/wallos/db/wallos.db /opt/wallos.db ```
OVERLORD commented 2026-02-04 16:25:10 +03:00
Author
Owner
Copy Link

@havardthom commented on GitHub (Nov 18, 2024):

@MickLesk did you test your change?

@havardthom commented on GitHub (Nov 18, 2024): @MickLesk did you test your change?
OVERLORD commented 2026-02-04 16:25:19 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 18, 2024):

Works fine for me. Why do you dont have an .db File? Is that a clean install without any user activity? Never registrated?

Ive build a little check, if the file is available for next pr. But it's still strange. It's there for me.

@MickLesk commented on GitHub (Nov 18, 2024): Works fine for me. Why do you dont have an .db File? Is that a clean install without any user activity? Never registrated? Ive build a little check, if the file is available for next pr. But it's still strange. It's there for me.
OVERLORD commented 2026-02-04 16:25:22 +03:00
Author
Owner
Copy Link

@Aloe-recite commented on GitHub (Nov 18, 2024):

Yes I have a DB. No it’s not clean, I’m updating from previous version. Ended up updating manually for the time being, after rolling back to a couple of versions ago (previous update broke images and I noticed just now).

@Aloe-recite commented on GitHub (Nov 18, 2024): Yes I have a DB. No it’s not clean, I’m updating from previous version. Ended up updating manually for the time being, after rolling back to a couple of versions ago (previous update broke images and I noticed just now).
OVERLORD commented 2026-02-04 16:25:25 +03:00
Author
Owner
Copy Link

@havardthom commented on GitHub (Nov 18, 2024):

Yes I have a DB. No it’s not clean, I’m updating from previous version. Ended up updating manually for the time being, after rolling back to a couple of versions ago (previous update broke images and I noticed just now).

Where is your DB? It should be here /opt/wallos/db/wallos.db, but the error you posted says it is missing

[ERROR] in line 66: exit code 0: while executing command mv /opt/wallos/db/wallos.db /opt/wallos.db
@havardthom commented on GitHub (Nov 18, 2024): > Yes I have a DB. No it’s not clean, I’m updating from previous version. Ended up updating manually for the time being, after rolling back to a couple of versions ago (previous update broke images and I noticed just now). Where is your DB? It should be here `/opt/wallos/db/wallos.db`, but the error you posted says it is missing ``` [ERROR] in line 66: exit code 0: while executing command mv /opt/wallos/db/wallos.db /opt/wallos.db ```
OVERLORD commented 2026-02-04 16:25:28 +03:00
Author
Owner
Copy Link

@Aloe-recite commented on GitHub (Nov 18, 2024):

it's indeed there and not empty too: /opt/wallos/db/wallos.db
Not sure why the script wants to move it to /opt/wallos.db though, shouldn't it stay in a "db" folder? Why is the script changing the current folder structure "/opt/Wallos/" with just /opt/ like in the first error above? With the current structure, manually updating is as easy as copying files over and running the migration command. I'm not an expert at all and just asking out of curiosity, I'm not implying anything so please don't feel bad about it.

Screenshot 2024-11-18 alle 20 51 36
@Aloe-recite commented on GitHub (Nov 18, 2024): it's indeed there and not empty too: /opt/wallos/db/wallos.db Not sure why the script wants to move it to /opt/wallos.db though, shouldn't it stay in a "db" folder? Why is the script changing the current folder structure "/opt/Wallos/<content>" with just /opt/<content> like in the first error above? With the current structure, manually updating is as easy as copying files over and running the migration command. I'm not an expert at all and just asking out of curiosity, I'm not implying anything so please don't feel bad about it. <img width="295" alt="Screenshot 2024-11-18 alle 20 51 36" src="https://github.com/user-attachments/assets/e922df13-a678-4e09-9b91-e38742887136">
OVERLORD commented 2026-02-04 16:25:35 +03:00
Author
Owner
Copy Link

@havardthom commented on GitHub (Nov 18, 2024):

We move what needs to be migrated out of the old app, remove the old app, get the new app, move migrated data into the new app. We don't want to copy files into the old app because that could mix old files with new files.
Anyway, if you now have /opt/wallos/db/wallos.db then the update should work for you after https://github.com/community-scripts/ProxmoxVE/pull/339 is merged. The problem in your post was that the images backup command failed, and that was after your database was moved, so when you tried to run the update again it could not find the database anymore

@havardthom commented on GitHub (Nov 18, 2024): We move what needs to be migrated out of the old app, remove the old app, get the new app, move migrated data into the new app. We don't want to copy files into the old app because that could mix old files with new files. Anyway, if you now have `/opt/wallos/db/wallos.db` then the update should work for you **after** https://github.com/community-scripts/ProxmoxVE/pull/339 is merged. The problem in [your post](https://github.com/community-scripts/ProxmoxVE/issues/315#issuecomment-2483634383) was that the images backup command failed, and that was after your database was moved, so when you tried to run the update again it could not find the database anymore
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#62
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?