Hi there,

I have cobbled together a CentOS 7 LAMP StackScript based on https://www.linode.com/stackscripts/view/335 and edited to change or remove various CentOS 5 functions and add my own, but it's not working. Some functions do succeed, but others (particularly the A, M and P functions) do not.

I don't see any reference in https://www.linode.com/docs/platform/stackscripts to viewing errors so that I can find out what is going wrong.

I *have* started writing a script from scratch, but I'm a bit pressed for time to set up a new server, so I thought that using an existing community StackScript would save me some time, but that is starting to look like it's exactly the opposite.

Any pointers to finding out what's happening with the results of a StackScript would be much appreciated. Thanks.


Craig

Managed to solve the issues with help from Linode support. You can, of course, run a StackScript from the command line to see if you get any errors, but it was looking to me like certain variables were not being passed to the StackScript by the Linode deployment interface.

However, turns out that the real problem -- which, as I allude to, could have been caught earlier if there was some sort of output from the StackScript execution by the deployment process -- was that there is no "mysql-server" in the CentOS 7 repos, and *that* is why everything to do with the MySQL function was failing. After modifying the StackScript to install MariaDB instead and using the newer "systemctl" to start the service, I finally had a working StackScript.

Like I say, access to some log output from a StackScript deployed during a rebuild would be helpful, rather than running blind. That's my suggestion to Linode.


Craig

StacksScript output method can vary with each StackScript, but their stdout/stderr by default goes to your console. Connect to Lish to watch them run.

-Chris

Hi Chris,

Thanks very much.


Craig