Dashboards autodeploys twice?

Been happening for a few versions now, if not always.

If I change the code on a dashboard, and save, the dashboard refreshes with the changes, and then 3 seconds later it does the same.

I imagine maybe PSU detects that the dashboard file has updated, and reloads it?

Product: PowerShell Universal
Version: 2.10

Are you saving the file on disk or via the admin console? I don’t see this when editing in the admin console but if you’re editing directly on disk I can imagine the file system watcher might be triggering one too many times.

Editing through the admin console, saved my changes, dashboard updates, counted 20 Mississippi’s (thought better to use yankee standards), and it redeployed again.

git only show one sync (push only).

it might be relevant to mention that I run multiple sites on the same server with IIS.

I’m not seeing anything alarming in the logs, though everytime I make a change, 2 of these ‘QuartzScheduler’ things appear.

[11:42:14 INF] Latest commit Id: 4ab1d3dead54825685585f55cc78624be0f12189, Number of changes since last sync: 2
[11:42:14 INF] Sync done. Status Id: 1
[11:42:14 INF] Scheduler QuartzScheduler_$_NON_CLUSTERED shutting down.
[11:42:14 INF] Scheduler QuartzScheduler_$_NON_CLUSTERED paused.
[11:42:14 INF] Scheduler QuartzScheduler_$_NON_CLUSTERED Shutdown complete.
[11:42:14 INF] Using object serializer: Quartz.Simpl.BinaryObjectSerializer, Quartz
[11:42:14 INF] Initialized Scheduler Signaller of type: Quartz.Core.SchedulerSignalerImpl
[11:42:14 INF] Quartz Scheduler created
[11:42:14 INF] RAMJobStore initialized.
[11:42:14 INF] Scheduler meta-data: Quartz Scheduler (v3.3.3.0) 'QuartzScheduler' with instanceId 'NON_CLUSTERED'
  Scheduler class: 'Quartz.Core.QuartzScheduler' - running locally.
  NOT STARTED.
  Currently in standby mode.
  Number of jobs executed: 0
  Using thread pool 'Quartz.Simpl.DefaultThreadPool' - with 100 threads.
  Using job-store 'Quartz.Simpl.RAMJobStore' - which does not support persistence. and is not clustered.

[11:42:14 INF] Quartz scheduler 'QuartzScheduler' initialized
[11:42:14 INF] Quartz scheduler version: 3.3.3.0
[11:42:14 INF] Scheduler QuartzScheduler_$_NON_CLUSTERED started.
[11:42:15 INF] Scheduler QuartzScheduler_$_NON_CLUSTERED shutting down.
[11:42:15 INF] Scheduler QuartzScheduler_$_NON_CLUSTERED paused.
[11:42:15 INF] Scheduler QuartzScheduler_$_NON_CLUSTERED Shutdown complete.
[11:42:15 INF] Using object serializer: Quartz.Simpl.BinaryObjectSerializer, Quartz
[11:42:15 INF] Initialized Scheduler Signaller of type: Quartz.Core.SchedulerSignalerImpl
[11:42:15 INF] Quartz Scheduler created
[11:42:15 INF] RAMJobStore initialized.
[11:42:15 INF] Scheduler meta-data: Quartz Scheduler (v3.3.3.0) 'QuartzScheduler' with instanceId 'NON_CLUSTERED'
  Scheduler class: 'Quartz.Core.QuartzScheduler' - running locally.
  NOT STARTED.
  Currently in standby mode.
  Number of jobs executed: 0
  Using thread pool 'Quartz.Simpl.DefaultThreadPool' - with 100 threads.
  Using job-store 'Quartz.Simpl.RAMJobStore' - which does not support persistence. and is not clustered.

[11:42:15 INF] Quartz scheduler 'QuartzScheduler' initialized
[11:42:15 INF] Quartz scheduler version: 3.3.3.0
[11:42:15 INF] Scheduler QuartzScheduler_$_NON_CLUSTERED started.
[11:42:15 INF] /UserLookup/Home
[11:42:15 INF] C:\inetpub\_Beta.MiddlewareDashboard\Modules\UniversalDashboard\3.12.0\Home
[11:42:15 INF] Client disconnected: jtolgpSfb5qNDmyv95ctjg

on another note, the git log in the admin console, suggests that every file related to my site has been “added” in every update

Interesting. I’ll have to setup git sync and test this out. I bet the git sync is triggering the dashboard reload for some reason.

1 Like

This is happening to me in 3.2.6 with two-way sync, double auto deploy reload. Do you know if this is related? Happy to open a separate issue.

2 Likes