forum.opsi.org

m.radtke hat geschrieben: ↑28 Sep 2023, 15:20 Hi

you can also download the package locally and start opsi-script locally to see where the script breaks. Exit Code is 1 so there's something wrong.

Regards
Mathias

Sorry for making late attempt. I tried again and analyzed it. The attached log image says, " /bin/bash: line 1: $: command not found" but "/bin/bash" exists.
As per log, the following is the place it breaks with exit code 127:
"/bin/bash -c "$installerSourceDir$ + "/new_touch_script.sh" || exit $?""
The following worked fine on the terminal:
"/bin/bash -c /tmp/new_touch_script.sh" || exit $?" (this working fine)

As you suggested, tried the package locally with opsi-script, and it breaks in the same place mentioned above.

Attached opsi-script log file. Eagerly waiting for your reply.

Edited again to attach the missed log file.

Regards,
arul

Maybe I delayed my reply!!

Should i have to start in a fresh thread or this same is this okay to continue?


Regards,
arul

Hi

could you please attach the opsiscript file?

Regards
Mathias

Thanks Mathias, for your reply.

Attached is setup.opsiscript file.

Hi

this should work theres a difference how to use opsi-script variables in primary and secondary sections. Primary sections like this you dont include the variable within the string of the command, in secondary sections, like shellInAnIcon, you do.

Regards
Mathias

Thanks Mathias,

It worked fine on local. Did the correction on opsi-server also, but from opsi-server getting same error. Attaching log image.

While i tried running from server, noticed it gets mounted for short time on "/media/opsi_depot/" with root permission, is it normal?

Thanks and Regards
arul

hmmm this seems odd.

could you upload the package somewhere and post the link?
I would like to take a deeper look and ask a colleague.

Regards
Mathias

Thanks for your interest,

Tried creating a new product "l-linux-script" to execute the same script, and got into the same issue, running fine locally but not from the server. Kept a copy of that also.
Kept it in Google Drive @:
https://drive.google.com/drive/folders/ ... sp=sharing

Thanks and Regards
arul

Hi Mathias,

Have very few hosts installed and installed the license around 2nd week of September. Attached is an image of validation. Hope it is not for validity issues.

Regards,
arul

soooo

it works with As the opsi-script interpreter uses double quotes arround the shellCall itself while interpreting, you have to use single quotes for the string part of the shellCall
Regards

Mathias