afg wrote:Actually that's not always the case. If your zonminder db is not named zm, one of the update SQL scripts will fail b/c it hard codes the database name. You can tell if this is the case if running zmupdate fails b/c it can't find the config table, after successfully running SOME of the updates.
See thread on lessons from 1.25 upgrade for how to fix.
Respectfully,
AG
I'm not sure how or why you think this statement is related to the issue the OP has described, but to answer your question as it relates to the "following the instructions" theme, you are not following the instructions if you are trying to change the name of the zoneminder database after the fact. The name of database is not hard coded. It is set at build time, just like many other variables. If for some unlikely reason you have to change the name of the database, and don't just simply want to, then what you should do is rebuild the ZoneMinder deb package to suit your tastes. In particular you need to set ZM_DB_NAME during the build. Instructions on how to do this are on our readthedocs site.
https://zoneminder.readthedocs.org/en/s ... index.html
br116 wrote:Did as suggested.
New partition, brand new 14.04 LTS, installed LAMP, followed bbunge instruction with copy and paste from a terminal from
https://wiki.zoneminder.com/Ubuntu_Serv ... e_easy_way
Got "it works" from Apache, but nothing else, no php, no ZM, no nothing. No log files.
Just giving up...
I'm sorry you are giving up, and I'm sure this is frustrating for you. However, statements like this are not particularly helpful in a technical support forum. Two things are certain in a forum such at this:
1) We aren't mind readers. We cannot see what you see, and simply stating something does or does not work w/o backing that up with real data is not helpful. Because you have not shown us what you did, that puts us into a guessing mode, which wastes everyone's time and frustrates everyone involved.
2) Instead, we need to see real data, copied and pasted, direct from your command prompt. Interpreting what is happening, in your own words, is not helpful. We also need to see your log files, again, copied and pasted. Not just a line or two, but a large amount. More is better. I know you made the statement "No log files", but that simply isn't true. You've demonstrated that the Apache web server is working, which means you are going to have an Apache log, and that is exactly what we need to see in order to learn what is happening.
TLDR
Maybe I'm just wasting my time by typing this, but if you find yourself back here, to increase the likeness of a better experience, backup any statements of something not working with exactly what you typed into the command prompt (your input) and the contents of any relevant logs files (the output). Asking how to do this is a valid question.