scheduled publish on umbraco 7.10.2 anyone had issues with it? setting date then doing save and schedule but it does not publish at that date. Item currently is not published.
So I know /umbraco/RestServices/ScheduledPublish/Index was the url for scheduled publish hitting that directly gives not found error, has that url changed?
Still think it's strange that server was elected as slave. That should only happen when there is already a server registered in the database that is elected as master.
Scheduled publish
scheduled publish on umbraco 7.10.2 anyone had issues with it? setting date then doing save and schedule but it does not publish at that date. Item currently is not published.
Anyone seen this before?
Regards
Ismail
Anything in the logs out of the ordinary ?
Nope, only thing of interest is
2018-04-12 16:02:00,740 [59] DEBUG Umbraco.Web.Scheduling.ScheduledPublishing - Does not run on slave servers. 2018-04-12 16:02:00,740 [59] DEBUG Umbraco.Web.Scheduling.ScheduledTasks - Does not run on slave servers. 2018-04-12 16:02:00,740 [59] DEBUG Umbraco.Web.Scheduling.BackgroundTaskRunner - [ScheduledPublishing] Task added Umbraco.Web.Scheduling.ScheduledPublishing 2018-04-12 16:02:00,740 [59] DEBUG Umbraco.Web.Scheduling.BackgroundTaskRunner - [ScheduledTasks] Task added Umbraco.Web.Scheduling.ScheduledTasks 2018-04-12 16:02:00,944 [59] DEBUG Umbraco.Core.Sync.DatabaseServerMessenger - Syncing from database... 2018-04-12 16:02:00,950 [59] DEBUG Umbraco.Core.Sync.DatabaseServerMessenger - Complete (took 6ms)
Also one thing is we are seeing http requests rather than https?
so
2018-04-12 16:02:05,436 [59] DEBUG Umbraco.Web.UmbracoModule - Begin request: http://oursite/umbraco/backoffice/UmbracoApi/Authentication/GetRemainingTimeoutSeconds.
Regards
Ismail
Ignore that https bit as this test server is not on https.
Hi Ismail,
Is this a loadbalanced setup.
I think you are on a slave server.
See source code : https://github.com/umbraco/Umbraco-CMS/blob/7ee510ed386495120666a78c61497f58ff05de8f/src/Umbraco.Web/Scheduling/KeepAlive.cs#L33
So I know /umbraco/RestServices/ScheduledPublish/Index was the url for scheduled publish hitting that directly gives not found error, has that url changed?
Dave,
Site is not load balanced. We have upgraded from 7.2.6 to 7.10.2.
Regards
Ismail
Than it's really strange.
The message should only show when you are on a slave server
https://github.com/umbraco/Umbraco-CMS/blob/7ee510ed386495120666a78c61497f58ff05de8f/src/Umbraco.Web/Scheduling/ScheduledPublishing.cs#L44
Can you try installing my loadbalancing dashboard plugin. This should give some indication on your setup. Just to be sure
Dave
Dave,
Just seen this https://our.umbraco.org/forum/using-umbraco-and-getting-started/85795-scheduled-publishing-doesnt-work and it looks like even though distributed is turned off i need to either set up umbracoApplicationUrl or register a master https://our.umbraco.org/documentation/getting-started/setup/server-setup/load-balancing/flexible-advanced#explicit-master-scheduling-server
Regards
Ismial
Maybe you can add this setting to your web.config
https://our.umbraco.org/documentation/Reference/Config/webconfig/#umbracodisableelectionforsingleserver-umbraco-v76
Dave
WOOOT GO ON DAVE MY SON.
That did the trick, many thanks for this as this was blocking or deployment as client uses this alot on their site.
Callum will get you a coffee at codegarden from me.
Regards
Ismail
Hi Ismail
Still think it's strange that server was elected as slave. That should only happen when there is already a server registered in the database that is elected as master.
https://github.com/umbraco/Umbraco-CMS/blob/7ee510ed386495120666a78c61497f58ff05de8f/src/Umbraco.Core/Services/ServerRegistrationService.cs#L81
So you are absolutely sure no 2 instances were connected to the same database ? Or maybe the db was a backup from a live load balanced environment ?
Dave
Db was live backup but not load balanced
That could be the issue. Because server election was enabled...there was probably a record in the db from the live server that was marked as active.
Because of this the test server was seen as extra server and elected as slave
Dave
is working on a reply...