On _lib/prod/lib/php/nm_ini_manager2.php, when I click on “Update production environment” the web interface becomes totally unresponsive and nothing happens.
Also the deployed sc app becomes unresponsive as well.
Can anyone confirm if the new “Update production environment” feature is working?
Same happening to me, running 9.9.019
@robydago , @ADon, when you click on the link to update production environment, you have to wait (and wait) until the screen with the option to verify updates appear. So Netmake should put a Loading… option like the same as in development option, when we try to update the SC version.
Something here but after 5 minutes I receive this message
Is this working for anyone yet? On Scritpcase 9.10 I am using the link from “Manage Production Environment” to “Update Production Environment”. All I get is a spinner that says ‘checking for updates’. I let it run for many hours and it never gets past that step.
I will never try this feature. If update for production is necessary, I will always test this first on my development system. If it works, I can publish the new production files too. If there is any error in the files of SC I don’t want to have problems in production. So I will not use this feature at all.
Greetings
Uwe
The feature works, but it requires a lot of memory. If nothing happens after starting, you need to look at the error log from the web server. This usually shows exactly where the problem lies.
In my case, it’s an in-house application, so you can test it. For customer installations, I would do the same as Uwe.
Now on version 9.11.000 (3). It is still not working. Same problem : when I click on “Update production environment” the web interface becomes totally unresponsive and nothing happens.
Also the deployed sc app becomes unresponsive as well.
Uploading the _lib folder does not make me very happy, It works but I have to reconfigure all my database connectios. Or can I exclude a folder wich contains this connections? Is this the one _lib\conf ?
Roelof
Dear @roelof
We carried out some tests to update the production environment via automatic update in the prod’s own interface, and despite the delay (there were major changes in this version, hence the delay), the environment was updated normally to version 1.0.002(1).
There was some instability in the service from last night to this morning, so it may have affected you in some way.
If you wish, you can also perform the manual update using the package (ZIP or TGZ) available on our website.
Best regards!
Same here, it’s running for 4 hours now
On the website it’s version scriptcase-prod-1.0.001 that is available.
Tried it again today on different servers. Everywhere the samen problem.
Ich mache es immer mit der zip-Datei die ich in der Produktionsumgebung dann entpacke. So häufig ist das ja nicht und es gab damit keine Probleme.
Liebe Grüße
Uwe Pfeiffer
Dear,
The link to download the production environment is now available on the website.
We apologize for the mistake, and if you have any questions, feel free to contact the support team (support@scriptcase.net)
Best regards!
This is still not working in v1.0.003 prod environment.
It basically hangs then gives a connection timeout error. (Would a ‘processing’ message and/or updatelog be so difficult?)
I’ve already increased the execution time to 3600 and the memory to 2GB to no avail.
CONTEXT:
The scriptcase changelog says you need to update the prod environment, but I’d already MANUALLY updated it to the latest version in the downloads some time before the specific changes indicated in the chagelog. (Why the hell doesn’t the changelog state the corect version of the prod environment to be used? ‘Latest version’ or just 'you’ll need to uptae the production enhvironment’ is imprecise and useless… what is the latest version? )
The latest version on the downloads was issued long before the specific changes referenced in the changelog, so I’d hoped to use the update functionality to bypass this imprecision.
I experienced a similar issue recently with Scriptcase 9. The “Update production environment” button caused my interface to hang as well. Clearing the browser cache and restarting the web server didn’t help, but re-deploying the entire application did resolve the problem temporarily. It seems like a bug in this Scriptcase version. I recommend reporting it to Scriptcase support and checking if an update or patch is available. You’re not alone with this issue!