Closed whitetiger264 closed 1 year ago
@whitetiger264 on a running VM I get this in the UI: on the stopped vm there is no option to take a volume snapshot so I browsed to the volume and took a snapshot there. this succeeded. I seem to be using the exact same JDK/JVM on an alma 8 env. Can you explain a bit more about the scenario you are following?
@whitetiger264 on a running VM I get this in the UI: on the stopped vm there is no option to take a volume snapshot so I browsed to the volume and took a snapshot there. this succeeded. I seem to be using the exact same JDK/JVM on an alma 8 env. Can you explain a bit more about the scenario you are following?
These are the exact steps I am taking:
Can you replicate this, also take note of the VM name you set try making one with example-date_year
@whitetiger264 on a running VM I get this in the UI: on the stopped vm there is no option to take a volume snapshot so I browsed to the volume and took a snapshot there. this succeeded. I seem to be using the exact same JDK/JVM on an alma 8 env. Can you explain a bit more about the scenario you are following?
These are the exact steps I am taking:
- I go to Compute -> Instance in UI.
- Stop the VM instance in question.
- Then go to Storage -> Volumes in UI.
- Look for the volume associated with the VM instance and select "Take Snapshot".
- Give it a name such as "VMName-Backup-23-June-2023".
- Select "Async" but I also tried without selecting this and then proceed to "OK".
- The process is started and throws this error.
Can you replicate this, also take note of the VM name you set try making one with example-date_year
I tried it now again. Two things I did differently:
cloudstack-management
, cloudstack-usage
and cloudstack-agent
. So that new Java processes are created.-
and _
characters and no spaces. And now it magically works:I tried another one now and used the -
character as before, it now works perfectly fine. The reason I rebooted cloudstack-management
, cloudstack-usage
and cloudstack-agent
was because of this guide:
Specifically this part:
a very weird error. I have restarted the server with the exact same jar and it's fine now. I can upload archives just fine
But I restarted the services instead of the server.
Someone then says the following below that thread:
This was probably caused when a Java security update was applied by CentOS, but running Java processes wasn't restarted.
This is most likely the same reason for Almalinux in my case. Since I can now no longer replicate this error, this report can be closed. Thank you.
ISSUE TYPE
COMPONENT NAME
CLOUDSTACK VERSION
CONFIGURATION
OS / ENVIRONMENT
SUMMARY
Volume snapshots failing due to possible Java issues.
STEPS TO REPRODUCE
Here's a log entry:
Specific Error:
Could not initialize class sun.nio.fs.UnixCopyFile
EXPECTED RESULTS
Normal Volume snapshot processing should execute as intended.