You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This appears to be a problem that has existed since daemon mode was created.
A NodeJS zowe command reports this when there is a syntax error in zowe.config.json:
-> zowe zosmf check status
[2021/11/02 12:11:55] [FATAL] [main.js:52] Error parsing JSON in the file 'C:\Users\ej608771\.zowe\zowe.config.json'.
Please check this configuration file for errors.
Error details: Unexpected token "
Line 97, Column 8
The current build of daemon mode reports the following. If the current build had previously started a daemon, the command simply hangs.
-> zowex_curr_build zosmf check status
Starting a background process to increase performance ...
The Zowe daemon that we started is not running on host = 127.0.0.1 with port = 4000.
Command used to start the Zowe daemon was:
C:\Program Files\nodejs\zowe.cmd --daemon
Terminating.
The original version of daemon mode also hangs when there is a syntax error in zowe.config.json.
The text was updated successfully, but these errors were encountered:
I think that you have caught the situation in which a configuration file is changed between zowex commands (after the daemon is started), but it still fails when the config file is wrong on the first zowex command (when it also tries to start the daemon). A very good thing is that we have no situation in which we hang.
We do NOT get the config syntax message, when the config file has a syntax error on first zowex command:
zowex_curr_build zosmf check status
Starting a background process to increase performance ...
The Zowe daemon that we started is not running on host = 127.0.0.1 with port = 4000.
Command used to start the Zowe daemon was:
C:\Program Files\nodejs\zowe.cmd --daemon
Terminating.
We properly get the config syntax message when the config file was good on the first zowex command, but the user introduced a syntax error into the config file before we run the command a second time:
zowex_curr_build zosmf check status
Command Preparation Failed:
Error parsing JSON in the file 'C:\Users\ej608771\.zowe\zowe.config.json'.
Please check this configuration file for errors.
Error details: Unexpected token "
Line 137, Column 4
This appears to be a problem that has existed since daemon mode was created.
A NodeJS zowe command reports this when there is a syntax error in zowe.config.json:
The current build of daemon mode reports the following. If the current build had previously started a daemon, the command simply hangs.
The original version of daemon mode also hangs when there is a syntax error in zowe.config.json.
The text was updated successfully, but these errors were encountered: