Everything posted by Isanderthul
-
Start/Stop Array via CLI
I needed to start the array from a different system, so I ended up doing this: #!/bin/bash CSRF=$(ssh [email protected] "sed -n 's/^csrf_token=//p' /var/local/emhttp/var.ini|tr -d '\"'") curl -k --data "startState=STOPPED&file=&csrf_token=${CSRF}&cmdStart=Start" http://192.168.88.235/update.htm
-
[Plugin] iSCSI Initiator
Thank you very much for your help. Everything is working. There were multiple problems with my server, first I had a library in the boot/extras that was breaking my user scripts. This prevented the script from mounting the unassigned device. Secondly the licence I had was at the limit of 6 devices, and I needed to upgrade my licence.
-
[Plugin] CA User Scripts
Ah now I realised I needed aaa_glibc-solibs-2.33-x86_64-3.txz for vim. But I need scripts more than I need vim... so 🤷♂️.
-
[Plugin] CA User Scripts
I think I might be causing this by installing aaa_glibc-solibs-2.33-x86_64-3.txz in my /boot/extras
-
[Plugin] CA User Scripts
Hi none of my scripts are running, so I have tried to manually run then the same way the plugin does ie echo /usr/local/emhttp/plugins/user.scripts/startBackground.php /tmp/user.scripts/tmpScripts/arrayStartup/script | at NOW -M > /dev/null 2>&1 and in the /var/log/syslog there is this error: Oct 4 10:42:51 Gen8 atd[9567]: PAM unable to dlopen(/lib64/security/pam_unix.so): /lib64/libc.so.6: version `GLIBC_2.32' not found (required by /lib64/libpthread.so.0) Oct 4 10:42:51 Gen8 atd[9567]: PAM adding faulty module: /lib64/security/pam_unix.so Oct 4 10:42:51 Gen8 kernel: atd[9567]: segfault at 0 ip 00001516594bf886 sp 00007ffc66660bb0 error 4 in libpthread-2.33.so[1516594bf000+f000] Oct 4 10:42:51 Gen8 kernel: Code: 00 48 c7 82 e8 02 00 00 e0 ff ff ff b8 11 01 00 00 66 48 0f 6e c7 66 0f 6c c0 0f 11 82 d8 02 00 00 0f 05 48 8b 05 3a 57 01 00 <48> 8b 00 64 48 89 04 25 98 06 00 00 0f b6 05 6f 5a 01 00 64 88 04
-
[Plugin] iSCSI Initiator
Hi @ich777 @dlandon, thank you very much for having a look. im happy my logs gave you some insight into the issue. I will try auto mounting the msa1040, we have it as an unassigned device, because it is not part of the array. I will try out a few suggested changes and let you know.
-
[Plugin] iSCSI Initiator
Hi. Thank you for the plugin we are using it to connect to our HPE MSA 1040. When the server reboots, the iSCSI connection is not re-established, and we have to do the following steps to get it going again: on the iscsi-initiator page: 1) Remove and Disconnect the existing Defined Target 2) Copy the Initiator Name into the Change Initiator Name text field, and click Change. 3) Populate the Create Connection text field with the target definition info as deleted in step 1, and click Create and Connect now the Active iSCSI sessions is showing the connection. on the Main page: click on the Mount button on the Device. Is there any way to automate this so that we dont have to redo it every time there is a reboot? Thank you.