Hello, If you want to upload from local you must offload the SSL certificate in your System VMs first. Because it try to upload the file over HTTPs and due to self sign or certificate error, it won’t let you upload.
Vivek Kumar Sr. Manager - Cloud & DevOps TechOps | Indiqus Technologies vivek.ku...@indiqus.com <mailto:vivek.ku...@indiqus.com> www.indiqus.com <https://www.indiqus.com/> > On 29-Jul-2022, at 11:33 PM, Airamek <vegkeppnemaira...@gmail.com> wrote: > > Thanks for the idea! I got in trough ssh, and it has some interesting errors. > > Jul 29 17:56:40 s-2-VM systemd[4111]: PAM _pam_load_conf_file: unable to open > config for /etc/pam.d/null > Jul 29 17:56:40 s-2-VM systemd[4111]: PAM error loading (null) > Jul 29 17:56:40 s-2-VM systemd[4111]: PAM failed: Critical error - immediate > abort > Jul 29 17:56:40 s-2-VM systemd[4111]: PAM _pam_init_handlers: error reading > /etc/pam.d/systemd-user > Jul 29 17:56:40 s-2-VM systemd[4111]: user@0.service: Failed to set up PAM > session: Operation not permitted > Jul 29 17:56:40 s-2-VM systemd[4111]: PAM _pam_init_handlers: [Critical error > - immediate abort] > Jul 29 17:56:40 s-2-VM systemd[4111]: user@0.service: Failed at step PAM > spawning /lib/systemd/systemd: Operation not permitted > ░░ Subject: Process /lib/systemd/systemd could not be executed > ░░ Defined-By: systemd > ░░ Support: https://www.debian.org/support > ░░ > ░░ The process /lib/systemd/systemd could not be executed and failed. > ░░ > ░░ The error number returned by this process is ERRNO. > Jul 29 17:56:40 s-2-VM systemd[4111]: PAM error reading PAM configuration file > Jul 29 17:56:40 s-2-VM systemd[4111]: PAM pam_start: failed to initialize > handlers > Jul 29 17:56:40 s-2-VM systemd[1]: user@0.service: Main process exited, > code=exited, status=224/PAM > > Any idea what could cause this? > > On 7/29/2022 7:42 PM, Sven Barczyk wrote: >> Hi, >> have you checked you SecStorageVM ? >> >> kind Regards >> Sven >> >> -----Ursprüngliche Nachricht----- >> Von: Airamek <vegkeppnemaira...@gmail.com> >> Gesendet: Freitag, 29. Juli 2022 19:30 >> An: users@cloudstack.apache.org >> Betreff: Can't upload ISO from local >> >> After a lot of trial and error, the system machines are running and their >> consoles are accessible, but I can't upload ISO files trough the web >> interface. I'm using version 4.17.0.1, and my setup consists of a management >> server with sql(MariaDB), and a hypervisor with the primary and secondary >> nfs shares running. Both machines are running Debian. >> >> The only error-like log I could find is in the syslog of the management >> server: >> >> Jul 29 19:19:08 laena java[5707]: WARN >> [c.c.a.d.ParamGenericValidationWorker] (qtp1648001170-17:ctx-29085af5 >> ctx-89738967) (logid:eafc7337) Received unknown parameters for command >> listZones. Unknown parameters : listall Jul 29 19:19:08 laena java[5707]: >> WARN [c.c.a.d.ParamGenericValidationWorker] (qtp1648001170-14:ctx-13826793 >> ctx-f1f86014) (logid:dff1eeea) Received unknown parameters for command >> listOsTypes. Unknown parameters : listall Jul 29 19:19:30 laena java[5707]: >> ERROR [c.c.a.AlertManagerImpl] >> (CapacityChecker:ctx-8d290200) (logid:c5703391) Caught exception in >> recalculating capacity Jul 29 19:19:30 laena java[5707]: >> java.lang.NullPointerException Jul 29 19:19:30 laena java[5707]: #011at >> com.cloud.configuration.ConfigurationManagerImpl.findPodAllocationState(ConfigurationManagerImpl.java:7170) >> Jul 29 19:19:30 laena java[5707]: #011at >> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native >> Method) >> Jul 29 19:19:30 laena java[5707]: #011at >> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) >> Jul 29 19:19:30 laena java[5707]: #011at >> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >> Jul 29 19:19:30 laena java[5707]: #011at >> java.base/java.lang.reflect.Method.invoke(Method.java:566) >> Jul 29 19:19:30 laena java[5707]: #011at >> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344) >> Jul 29 19:19:30 laena java[5707]: #011at >> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198) >> Jul 29 19:19:30 laena java[5707]: #011at >> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163) >> Jul 29 19:19:30 laena java[5707]: #011at >> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:97) >> Jul 29 19:19:30 laena java[5707]: #011at >> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186) >> Jul 29 19:19:30 laena java[5707]: #011at >> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:215) >> Jul 29 19:19:30 laena java[5707]: #011at >> com.sun.proxy.$Proxy122.findPodAllocationState(Unknown Source) Jul 29 >> 19:19:30 laena java[5707]: #011at >> com.cloud.alert.AlertManagerImpl.recalculateCapacity(AlertManagerImpl.java:345) >> Jul 29 19:19:30 laena java[5707]: #011at >> com.cloud.alert.AlertManagerImpl.checkForAlerts(AlertManagerImpl.java:465) >> Jul 29 19:19:30 laena java[5707]: #011at >> com.cloud.alert.AlertManagerImpl$CapacityChecker.runInContext(AlertManagerImpl.java:455) >> Jul 29 19:19:30 laena java[5707]: #011at >> org.apache.cloudstack.managed.context.ManagedContextTimerTask$1.runInContext(ManagedContextTimerTask.java:30) >> Jul 29 19:19:30 laena java[5707]: #011at >> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48) >> Jul 29 19:19:30 laena java[5707]: #011at >> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55) >> Jul 29 19:19:30 laena java[5707]: #011at >> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102) >> Jul 29 19:19:30 laena java[5707]: #011at >> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52) >> Jul 29 19:19:30 laena java[5707]: #011at >> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45) >> Jul 29 19:19:30 laena java[5707]: #011at >> org.apache.cloudstack.managed.context.ManagedContextTimerTask.run(ManagedContextTimerTask.java:32) >> Jul 29 19:19:30 laena java[5707]: #011at >> java.base/java.util.TimerThread.mainLoop(Timer.java:556) >> Jul 29 19:19:30 laena java[5707]: #011at >> java.base/java.util.TimerThread.run(Timer.java:506) >> Jul 29 19:20:01 laena java[5707]: INFO [c.c.s.StatsCollector] >> (StatsCollector-5:ctx-ce26ac6f) (logid:2cf448bc) system memory from >> /proc: 8252907520 >> Jul 29 19:20:01 laena java[5707]: INFO [c.c.s.StatsCollector] >> (StatsCollector-5:ctx-ce26ac6f) (logid:2cf448bc) free memory from /proc: >> 5333086208 >> Jul 29 19:20:01 laena java[5707]: INFO [c.c.s.StatsCollector] >> (StatsCollector-5:ctx-ce26ac6f) (logid:2cf448bc) used memory from /proc: >> 1101472 >> >> I attached a screenshot of the error the WebGUI gives when trying to add the >> ISO. >> >> Thanks for any help in advance! -- This message is intended only for the use of the individual or entity to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient, please delete the original message and any copy of it from your computer system. You are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited unless proper authorization has been obtained for such action. If you have received this communication in error, please notify the sender immediately. Although IndiQus attempts to sweep e-mail and attachments for viruses, it does not guarantee that both are virus-free and accepts no liability for any damage sustained as a result of viruses.
