Upgrading SAS 9.4 M4 to SAS 9.4 M7 - Error during Configuration SAS Compute

[junny]

Hi Experts,

We are performing an update in place of SAS Server (compute) 9.4 M4 to 9.4 M7, we got an error during configuration phase Stage 2 Start Spawners - Step 2 SAS Web Infrastructure Platform Scheduling Services

Log shows this error message:

[startCacheLocator] 2021-01-16 02:40:24,056 [main] INFO com.sas.sdw.SDWExceptionHandler - message=An unexpected error occurred. Please refer to /hadoop/installation/Config/Lev2/Logs/Configure/wipschedsvcs_startServer_2021-01-16-02.40.21.log for more details.
[propertyfile] Updating property file: /hadoop/installation/Config/Lev2/Logs/Configure/wipschedsvcs_config_status.properties
[propertyfile] Updating property file: /hadoop/installation/Config/Lev2/Logs/Configure/wipschedsvcs_config_status.properties
2021-01-16 02:40:24,070 [main] INFO com.sas.sdw.SDWExceptionHandler - configStatusFile set.
2021-01-16 02:40:24,074 [main] ERROR com.sas.sdw.SDWExceptionHandler - com.sas.sdw.SDWException: An unexpected error occurred. Please refer to /hadoop/installation/Config/Lev2/Logs/Configure/wipschedsvcs_startServer_2021-01-16-02.40.21.log for more details.

....

Caused by: java.lang.IllegalArgumentException: directory is a required attribute for task startCacheLocator!

Please someone has any idea?.

Thanks and best regars,

JZ

[SASKiwi]

What are the details in the highlighted configuration log?

[junny]

Hi SASKiwi,

Attached you will find the configuration log with errors.

Thanks,

[SASKiwi]

Is the log you have posted this one?

/hadoop/installation/Config/Lev2/Logs/Configure/wipschedsvcs_startServer_2021-01-16-02.40.21.log

It doesn't provide any more details on errors than you have already posted. The suggestion is you have missed out a directory in one of the configuration inputs. Maybe more experienced installers like @AnandVyas can help. Of course SAS Tech Support is your other option.

[AnandVyas]

Hi @junny 

Error in the log only says about cachelocator directory. Can you check if it's exists and you can successfully start the service directly on server? If yes, try running the wizard again. If not, then as suggested by @SASKiwi it's best to reach out to SAS TS.

[junny]

Hi Anand_V,
I can not see in the log which directory of cachelocator is requested. I started that service manually with sucess and go back to the wizard to retry but I got same error.
We restored from the latest backup working state of server and apply the upgrade process again.

Thanks & Regards,
Junny

[SASKiwi]

@junny  - Did that fix the problem?

[junny]

Hi @SASKiwi,

We don’t know yet, awaiting for a new downtime to repeat the process.

Thanks and best regards,
J

[junny · Accepted solution]

Hi All,

Finally, we could solve this error.
The issue was that we were upgrading a server (running linux) that was restored from a backup copied using “cp” command, that made changes on file dates of original files on /SASHome/ SASFoundation/9.4/sasexe/ and more important files of the installation, so when the upgrade process is running installation, it validates dates on files older than date of new version for replacing.

We could repeat process with success by changing dates of all files under /SASHome/ directory with a very old date (lower than M7 was released), and everything was fine.

Thanks & Best regards,
J