UCD WAS Config plugin can't find the WAS installation - udeploy

My WAS 8.5 is installed in C:\Program Files(x86)\IBM\WebSphere\AppServer\bin\wsadmin.bat. How can I tell the discovery process to look at my installation location?
plugin: WAS - Deploy, id: com.urbancode.air.plugin.WebSphere, version: 98
plugin command: 'cmd' '/C' '""C:\Program Files\ibm-ucd\agent\opt\groovy-1.8.8\bin\groovy" -cp "C:\Program Files\ibm-ucd\agent\var\plugins\com.urbancode.air.plugin.WebSphere_98_b9f10d322ce14ba5b38aa4757ce3ac59f5ec7643b2b922935ccab03536b404a2\classes;C:\Program Files\ibm-ucd\agent\var\plugins\com.urbancode.air.plugin.WebSphere_98_b9f10d322ce14ba5b38aa4757ce3ac59f5ec7643b2b922935ccab03536b404a2\lib\uDeployRestClient.jar;C:\Program Files\ibm-ucd\agent\var\plugins\com.urbancode.air.plugin.WebSphere_98_b9f10d322ce14ba5b38aa4757ce3ac59f5ec7643b2b922935ccab03536b404a2\lib\jettison-1.1.jar" "C:\Program Files\ibm-ucd\agent\var\plugins\com.urbancode.air.plugin.WebSphere_98_b9f10d322ce14ba5b38aa4757ce3ac59f5ec7643b2b922935ccab03536b404a2\wasDiscovery.groovy" "C:\Program Files\ibm-ucd\agent\var\temp\logs8306861047267428227\input.props" "C:\Program Files\ibm-ucd\agent\var\temp\logs8306861047267428227\output.props""'
working directory: C:\Program Files\ibm-ucd\agent\var\temp
properties:
PLUGIN_INPUT_PROPS=C:\Program Files\ibm-ucd\agent\var\temp\logs8306861047267428227\input.props
PLUGIN_OUTPUT_PROPS=C:\Program Files\ibm-ucd\agent\var\temp\logs8306861047267428227\output.props
pathOverride=
profilePathAgent=
profilePathResource=
resourcePath=/Topology Discovery/T500
environment:
AGENT_HOME=C:\Program Files\ibm-ucd\agent
AH_WEB_URL=https://localhost:8443
AUTH_TOKEN=****
DS_SYSTEM_ENCODING=Cp1252
JAVA_OPTS=-Dfile.encoding=Cp1252 -Dconsole.encoding=Cp1252
PLUGIN_HOME=C:\Program Files\ibm-ucd\agent\var\plugins\com.urbancode.air.plugin.WebSphere_98_b9f10d322ce14ba5b38aa4757ce3ac59f5ec7643b2b922935ccab03536b404a2
UD_DIALOGUE_ID=4f5c360e-69e0-4f52-87e0-6dfc6b5e01a1
================================================================================
**Checking path for WebSphere install: C:\Program Files\IBM\WebSphere\AppServer\bin\wsadmin.bat
Checking path for WebSphere install: C:\IBM\WebSphere\AppServer\bin\wsadmin.bat
WebSphere installation not found. Ending discovery process.**

Set the wsadmin.path property on the agent resource to the location of the wsadmin file. See step 2 in the following document:
https://www.ibm.com/support/knowledgecenter/SS4GSP_6.2.2/com.ibm.udeploy.doc/topics/resources_import_was.html

Related

ActiveMQ Artemis stopping automatically. localhost is not loading

I have installed ActiveMQ Artemis on my office laptop. I created a broker, and from the broker's bin folder I ran artemis-exe install.
Then after that I ran the start command. It shows it has started but, when I check status it shows stopped. I cannot access localhost:8161. Here is my log file:
2020-09-07 12:30:45,458 DEBUG - Starting WinSW in the CLI mode
2020-09-07 12:30:46,033 INFO - Starting the service with id 'artemis-btBroker-0.0.0.0'
2020-09-07 12:30:46,737 DEBUG - Starting WinSW in the service mode
2020-09-07 12:30:46,837 DEBUG - Completed. Exit code is 0
2020-09-07 12:30:46,881 INFO - Starting %JAVA_HOME%\bin\java.exe -Xbootclasspath/a:C:\Users\613379463\Downloads\apache-artemis-2.15.0-bin\apache-artemis-2.15.0\lib\jboss-logmanager-2.1.10.Final.jar;C:\Users\613379463\Downloads\apache-artemis-2.15.0-bin\apache-artemis-2.15.0\lib\wildfly-common-1.5.2.Final.jar -XX:+UseParallelGC -Xms512M -Xmx1024M -classpath C:\Users\613379463\Downloads\apache-artemis-2.15.0-bin\apache-artemis-2.15.0\lib\artemis-boot.jar -Dartemis.home=C:\Users\613379463\Downloads\apache-artemis-2.15.0-bin\apache-artemis-2.15.0 -Dartemis.instance=C:\Users\613379463\Downloads\apache-artemis-2.15.0-bin\apache-artemis-2.15.0\bin\btBroker -Ddata.dir=C:\Users\613379463\Downloads\apache-artemis-2.15.0-bin\apache-artemis-2.15.0\bin\btBroker\data -Dartemis.instance.etc=C:\Users\613379463\Downloads\apache-artemis-2.15.0-bin\apache-artemis-2.15.0\bin\btBroker\etc -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dlogging.configuration=file:/C:/Users/613379463/Downloads/apache-artemis-2.15.0-bin/apache-artemis-2.15.0/bin/btBroker/etc//logging.properties -Djava.security.auth.login.config=C:\Users\613379463\Downloads\apache-artemis-2.15.0-bin\apache-artemis-2.15.0\bin\btBroker\etc\login.config -Dhawtio.realm=activemq -Dhawtio.offline="true" -Dhawtio.role=amq -Dhawtio.rolePrincipalClasses=org.apache.activemq.artemis.spi.core.security.jaas.RolePrincipal -Djolokia.policyLocation=file:/C:/Users/613379463/Downloads/apache-artemis-2.15.0-bin/apache-artemis-2.15.0/bin/btBroker/etc//jolokia-access.xml org.apache.activemq.artemis.boot.Artemis run
2020-09-07 12:30:47,081 DEBUG - Completed. Exit code is 0
The Artemis ActiveMQ service is known to start and immediately stop (without any errors shown on command line) if %JAVA_HOME% is not set, as Apurv Adarsh's comment mentions.
The solution is to set the env var and then run the service as normal, as follows:
(1) Set JAVA_HOME
Verify %JAVA_HOME% system environment variable exists:
echo $Env:JAVA_HOME # from PowerShell
echo %JAVA_HOME% # from cmd
# e.g. 'C:\Program Files\Java\jdk-10.0.2\'
# or blank if not set.
if not, find java.exe (download/install, if necessary):
> where.exe java.exe # from PowerShell
> where java.exe # from cmd
# C:\Program Files (x86)\Common Files\Oracle\Java\javapath\java.exe
# C:\Program Files\Java\jdk-10.0.2\bin\java.exe
Set JAVA_HOME env var, I'll choose the jdk-10.0.2 version. /M will set as system variable, instead of user var. btw, no need to include '/bin/java.exe'
> setx /M JAVA_HOME "C:\Program Files\Java\"
SUCCESS: Specified value was saved.
(Restart the prompt to load the newly set env variable.)
(2) Install & Start Artemis Windows Service
cd into Artemis ActiveMQ root directory. Let my_broker be the name of the broker instance already created.
Ensure service is installed, then start:
> "my_broker/bin/artemis-service" install
...
> "my_broker/bin/artemis-service" start
2021-01-01 12:00:00,000 INFO - Starting the service with id 'artemis-my_broker-0.0.0.0'
(3) Check Running Status:
Verify service status is running:
> "my_broker/bin/artemis-service" status
Started

Azure DevOps npm install fails with post install script errors for node-sass 4.9.0

I'm trying to run a build. I've made very minor changes since the last build ran (about 5 months ago) but now I can't get past npm install.
Here's some excerpts of the log - I'd post more but SO won't let me as its so big...
2020-01-29T13:32:00.3347468Z ##[section]Starting: npm install
2020-01-29T13:32:00.3445773Z ==============================================================================
2020-01-29T13:32:00.3445826Z Task : npm
2020-01-29T13:32:00.3445864Z Description : Install and publish npm packages, or run an npm command. Supports npmjs.com and authenticated registries like Azure Artifacts.
2020-01-29T13:32:00.3445892Z Version : 1.161.0
2020-01-29T13:32:00.3445917Z Author : Microsoft Corporation
2020-01-29T13:32:00.3445967Z Help : https://learn.microsoft.com/azure/devops/pipelines/tasks/package/npm
2020-01-29T13:32:00.3445994Z ==============================================================================
2020-01-29T13:32:00.7920586Z SYSTEMVSSCONNECTION exists true
2020-01-29T13:32:00.9489042Z SYSTEMVSSCONNECTION exists true
2020-01-29T13:32:01.3438318Z [command]C:\windows\system32\cmd.exe /D /S /C ""C:\Program Files\nodejs\npm.cmd" --version"
2020-01-29T13:32:11.3468119Z 6.13.4
2020-01-29T13:32:13.4260298Z [command]C:\windows\system32\cmd.exe /D /S /C ""C:\Program Files\nodejs\npm.cmd" config list"
2020-01-29T13:32:13.9747579Z ; cli configs
2020-01-29T13:32:13.9748043Z metrics-registry = "https://registry.npmjs.org/"
2020-01-29T13:32:13.9748226Z scope = ""
2020-01-29T13:32:13.9748386Z user-agent = "npm/6.13.4 node/v12.14.1 win32 x64"
2020-01-29T13:32:13.9748504Z
2020-01-29T13:32:13.9748640Z ; environment configs
2020-01-29T13:32:13.9748792Z cache = "C:\\npm\\cache"
2020-01-29T13:32:13.9748951Z prefix = "C:\\npm\\prefix"
2020-01-29T13:32:13.9749077Z userconfig = "D:\\a\\1\\npm\\124.npmrc"
2020-01-29T13:32:13.9749211Z
2020-01-29T13:32:13.9749338Z ; builtin config undefined
2020-01-29T13:32:13.9749449Z
2020-01-29T13:32:13.9749576Z ; node bin location = C:\Program Files\nodejs\node.exe
2020-01-29T13:32:13.9749724Z ; cwd = D:\a\1\s\src\Ministryweb
2020-01-29T13:32:13.9749849Z ; HOME = C:\Users\VssAdministrator
2020-01-29T13:32:13.9750000Z ; "npm config ls -l" to show all defaults.
2020-01-29T13:32:13.9750146Z
2020-01-29T13:32:13.9803873Z [command]C:\windows\system32\cmd.exe /D /S /C ""C:\Program Files\nodejs\npm.cmd" install"
2020-01-29T13:34:15.6513894Z
2020-01-29T13:34:15.6514788Z > node-sass#4.9.0 install D:\a\1\s\src\Ministryweb\node_modules\node-sass
2020-01-29T13:34:15.6514976Z > node scripts/install.js
2020-01-29T13:34:15.6515158Z
2020-01-29T13:34:15.6515339Z Downloading binary from https://github.com/sass/node-sass/releases/download/v4.9.0/win32-x64-72_binding.node
2020-01-29T13:34:15.6515564Z
2020-01-29T13:34:15.6515739Z > node-sass#4.9.0 postinstall D:\a\1\s\src\Ministryweb\node_modules\node-sass
2020-01-29T13:34:15.6515874Z > node scripts/build.js
2020-01-29T13:34:15.6515991Z
2020-01-29T13:34:15.6516160Z Building: C:\Program Files\nodejs\node.exe D:\a\1\s\src\Ministryweb\node_modules\node-gyp\bin\node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
2020-01-29T13:34:15.6516306Z Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
2020-01-29T13:34:15.6516469Z Build started 1/29/2020 1:32:48 PM.
2020-01-29T13:34:15.6516640Z Project "D:\a\1\s\src\Ministryweb\node_modules\node-sass\build\binding.sln" on node 1 (default targets).
2020-01-29T13:34:15.6516772Z ValidateSolutionConfiguration:
2020-01-29T13:34:15.6516907Z Building solution configuration "Release|x64".
2020-01-29T13:34:15.6517083Z Project "D:\a\1\s\src\Ministryweb\node_modules\node-sass\build\binding.sln" (1) is building "D:\a\1\s\src\Ministryweb\node_modules\node-sass\build\binding.vcxproj.metaproj" (2) on node 1 (default targets).
2020-01-29T13:34:15.6517456Z Project "D:\a\1\s\src\Ministryweb\node_modules\node-sass\build\binding.vcxproj.metaproj" (2) is building "D:\a\1\s\src\Ministryweb\node_modules\node-sass\build\src\libsass.vcxproj" (3) on node 1 (default targets).
2020-01-29T13:34:15.6517700Z PrepareForBuild:
2020-01-29T13:34:15.6517847Z Creating directory "Release\obj\libsass\".
2020-01-29T13:34:15.6519124Z Creating directory "D:\a\1\s\src\Ministryweb\node_modules\node-sass\build\Release\".
2020-01-29T13:34:15.6519299Z Creating directory "Release\obj\libsass\libsass.tlog\".
2020-01-29T13:34:15.6519429Z InitializeBuildStatus:
2020-01-29T13:34:15.6519566Z Creating "Release\obj\libsass\libsass.tlog\unsuccessfulbuild" because "AlwaysCreate" was specified.
2020-01-29T13:34:15.6519727Z ClCompile:
2020-01-29T13:34:15.6520514Z C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Tools\MSVC\14.16.27023\bin\HostX64\x64\CL.exe /c /I"C:\Users\VssAdministrator\.node-gyp\12.14.1\include\node" /I"C:\Users\VssAdministrator\.node-gyp\12.14.1\src" /I"C:\Users\VssAdministrator\.node-gyp\12.14.1\deps\uv\include" /I"C:\Users\VssAdministrator\.node-gyp\12.14.1\deps\v8\include" /I..\..\src\libsass\include /Z7 /nologo /W3 /WX- /diagnostics:classic /MP /Ox /Ob2 /Oi /Ot /Oy /D NODE_GYP_MODULE_NAME=libsass /D USING_UV_SHARED=1 /D USING_V8_SHARED=1 /D V8_DEPRECATION_WARNINGS=1 /D V8_DEPRECATION_WARNINGS /D V8_IMMINENT_DEPRECATION_WARNINGS /D WIN32 /D _CRT_SECURE_NO_DEPRECATE /D _CRT_NONSTDC_NO_DEPRECATE /D _HAS_EXCEPTIONS=0 /D OPENSSL_NO_PINSHARED /D OPENSSL_THREADS /D "LIBSASS_VERSION=\"3.5.4\"" /GF /Gm- /MT /GS /Gy /fp:precise /Qspectre /Zc:wchar_t /Zc:forScope /Zc:inline /GR- /Fo"Release\obj\libsass\\" /Fd"Release\obj\libsass\libsass.pdb" /Gd /TP /wd4351 /wd4355 /wd4800 /wd4251 /wd4275 /wd4244 /wd4267 /FC /errorReport:queue /GR /EHsc ..\..\src\libsass\src\ast.cpp ..\..\src\libsass\src\ast_fwd_decl.cpp ..\..\src\libsass\src\backtrace.cpp ..\..\src\libsass\src\base64vlq.cpp ..\..\src\libsass\src\bind.cpp ..\..\src\libsass\src\check_nesting.cpp ..\..\src\libsass\src\color_maps.cpp ..\..\src\libsass\src\constants.cpp ..\..\src\libsass\src\context.cpp ..\..\src\libsass\src\cssize.cpp ..\..\src\libsass\src\emitter.cpp ..\..\src\libsass\src\environment.cpp ..\..\src\libsass\src\error_handling.cpp ..\..\src\libsass\src\eval.cpp ..\..\src\libsass\src\expand.cpp ..\..\src\libsass\src\extend.cpp ..\..\src\libsass\src\file.cpp ..\..\src\libsass\src\functions.cpp ..\..\src\libsass\src\inspect.cpp ..\..\src\libsass\src\json.cpp ..\..\src\libsass\src\lexer.cpp ..\..\src\libsass\src\listize.cpp ..\..\src\libsass\src\memory\SharedPtr.cpp ..\..\src\libsass\src\node.cpp ..\..\src\libsass\src\operators.cpp ..\..\src\libsass\src\output.cpp ..\..\src\libsass\src\parser.cpp ..\..\src\libsass\src\plugins.cpp ..\..\src\libsass\src\position.cpp ..\..\src\libsass\src\prelexer.cpp ..\..\src\libsass\src\remove_placeholders.cpp ..\..\src\libsass\src\sass.cpp ..\..\src\libsass\src\sass2scss.cpp ..\..\src\libsass\src\sass_context.cpp ..\..\src\libsass\src\sass_functions.cpp ..\..\src\libsass\src\sass_util.cpp ..\..\src\libsass\src\sass_values.cpp ..\..\src\libsass\src\source_map.cpp ..\..\src\libsass\src\subset_map.cpp ..\..\src\libsass\src\to_c.cpp ..\..\src\libsass\src\to_value.cpp ..\..\src\libsass\src\units.cpp ..\..\src\libsass\src\utf8_string.cpp ..\..\src\libsass\src\util.cpp ..\..\src\libsass\src\values.cpp
2020-01-29T13:34:15.6521162Z cl : Command line warning D9025: overriding '/GR-' with '/GR' [D:\a\1\s\src\Ministryweb\node_modules\node-sass\build\src\libsass.vcxproj]
2020-01-29T13:34:15.6521358Z cl : Command line warning D9025: overriding '/GR-' with '/GR' [D:\a\1\s\src\Ministryweb\node_modules\node-sass\build\src\libsass.vcxproj]
2020-01-29T13:34:15.6521493Z ast.cpp
2020-01-29T13:34:15.6521625Z cl : Command line warning D9025: overriding '/GR-' with '/GR' [D:\a\1\s\src\Ministryweb\node_modules\node-sass\build\src\libsass.vcxproj]
-- ABBREVIATED --
2020-01-29T13:34:15.7628892Z 11784 silly postinstall sass-graph#2.2.4
2020-01-29T13:34:15.7628923Z 11785 info lifecycle sass-graph#2.2.4~postinstall: sass-graph#2.2.4
2020-01-29T13:34:15.7628952Z 11786 silly postinstall node-sass#4.9.0
2020-01-29T13:34:15.7628986Z 11787 info lifecycle node-sass#4.9.0~postinstall: node-sass#4.9.0
2020-01-29T13:34:15.7629016Z 11788 verbose lifecycle node-sass#4.9.0~postinstall: unsafe-perm in lifecycle true
2020-01-29T13:34:15.7629354Z 11789 verbose lifecycle node-sass#4.9.0~postinstall: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;D:\a\1\s\src\Ministryweb\node_modules\node-sass\node_modules\.bin;D:\a\1\s\src\Ministryweb\node_modules\.bin;C:\hostedtoolcache\windows\NuGet\4.4.1\x64;C:\agents\2.164.6\externals\git\cmd;C:/hostedtoolcache/windows\Python\3.6.8\x64;C:/hostedtoolcache/windows\Python\3.6.8\x64\Scripts;C:\Program Files\Mercurial\;C:\ProgramData\kind;C:\vcpkg;C:\cf-cli;C:\Program Files (x86)\NSIS\;C:\Program Files\Mercurial\;C:\Program Files\Boost\1.69.0;C:\Program Files\dotnet;C:\mysql-5.7.21-winx64\bin;C:\Program Files\Java\zulu-8-azure-jdk_8.40.0.25-8.0.222-win_x64\bin;C:\Program Files (x86)\sbt\bin;C:\Rust\.cargo\bin;C:\hostedtoolcache\windows\Ruby\2.5.7\x64\bin;C:\Go1.12.7\bin;C:\hostedtoolcache\windows\Python\3.6.8\x64\Scripts;C:\hostedtoolcache\windows\Python\3.6.8\x64;C:\npm\prefix;C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\wbin;C:\Program Files\Microsoft MPI\Bin\;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\;C:\ProgramData\Chocolatey\bin;C:\Program Files\Docker;C:\Program Files\PowerShell\6\;C:\Program Files\dotnet\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\120\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\130\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\140\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\150\DTS\Binn\;C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\;C:\Program Files\Microsoft Service Fabric\bin\Fabric\Fabric.Code;C:\Program Files\Microsoft SDKs\Service Fabric\Tools\ServiceFabricLocalClusterManager;C:\Program Files\nodejs\;C:\Program Files\Git\cmd;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\bin;c:\tools\php;C:\Program Files (x86)\sbt\bin;C:\Program Files (x86)\Subversion\bin;C:\SeleniumWebDrivers\ChromeDriver\;C:\ProgramData\chocolatey\lib\maven\apache-maven-3.6.2\bin;C:\Program Files\CMake\bin;C:\Strawberry\c\bin;C:\Strawberry\perl\site\bin;C:\Strawberry\perl\bin;C:\Program Files\OpenSSL\bin;C:\Users\VssAdministrator\.dotnet\tools;C:\Program Files (x86)\Microsoft SQL Server\13
2020-01-29T13:34:15.7629678Z 11790 verbose lifecycle node-sass#4.9.0~postinstall: CWD: D:\a\1\s\src\Ministryweb\node_modules\node-sass
2020-01-29T13:34:15.7629714Z 11791 silly lifecycle node-sass#4.9.0~postinstall: Args: [ '/d /s /c', 'node scripts/build.js' ]
2020-01-29T13:34:15.7629751Z 11792 silly lifecycle node-sass#4.9.0~postinstall: Returned: code: 1 signal: null
2020-01-29T13:34:15.7629793Z 11793 info lifecycle node-sass#4.9.0~postinstall: Failed to exec postinstall script
2020-01-29T13:34:15.7629823Z 11794 timing action:postinstall Completed in 95942ms
2020-01-29T13:34:15.7629857Z 11795 verbose unlock done using C:\npm\cache\_locks\staging-30fa0784d58eff0a.lock for D:\a\1\s\src\Ministryweb\node_modules\.staging
2020-01-29T13:34:15.7629894Z 11796 timing stage:rollbackFailedOptional Completed in 628ms
2020-01-29T13:34:15.7629930Z 11797 timing stage:runTopLevelLifecycles Completed in 114608ms
-- ABBREVIATED --
2020-01-29T13:34:15.7646802Z 11798 silly saveTree `-- node-sass#4.9.0
2020-01-29T13:34:15.7646831Z 11799 verbose stack Error: node-sass#4.9.0 postinstall: `node scripts/build.js`
2020-01-29T13:34:15.7646859Z 11799 verbose stack Exit status 1
2020-01-29T13:34:15.7646897Z 11799 verbose stack at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
2020-01-29T13:34:15.7646933Z 11799 verbose stack at EventEmitter.emit (events.js:223:5)
2020-01-29T13:34:15.7646967Z 11799 verbose stack at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
2020-01-29T13:34:15.7647002Z 11799 verbose stack at ChildProcess.emit (events.js:223:5)
2020-01-29T13:34:15.7647032Z 11799 verbose stack at maybeClose (internal/child_process.js:1021:16)
2020-01-29T13:34:15.7647068Z 11799 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
2020-01-29T13:34:15.7647101Z 11800 verbose pkgid node-sass#4.9.0
2020-01-29T13:34:15.7647129Z 11801 verbose cwd D:\a\1\s\src\Ministryweb
2020-01-29T13:34:15.7647157Z 11802 verbose Windows_NT 10.0.14393
2020-01-29T13:34:15.7647190Z 11803 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
2020-01-29T13:34:15.7647228Z 11804 verbose node v12.14.1
2020-01-29T13:34:15.7647255Z 11805 verbose npm v6.13.4
2020-01-29T13:34:15.7647282Z 11806 error code ELIFECYCLE
2020-01-29T13:34:15.7647311Z 11807 error errno 1
2020-01-29T13:34:15.7647341Z 11808 error node-sass#4.9.0 postinstall: `node scripts/build.js`
2020-01-29T13:34:15.7647369Z 11808 error Exit status 1
2020-01-29T13:34:15.7647397Z 11809 error Failed at the node-sass#4.9.0 postinstall script.
2020-01-29T13:34:15.7647432Z 11809 error This is probably not a problem with npm. There is likely additional logging output above.
2020-01-29T13:34:15.7647466Z 11810 verbose exit [ 1, true ]
2020-01-29T13:34:15.7647484Z
2020-01-29T13:34:15.7690666Z ##[error]Error: Npm failed with return code: 1
2020-01-29T13:34:15.7699335Z ##[section]Finishing: npm install
This seems to be an error compiling Python code but beyond that, I'm at sea here. Any ideas why this may have started failing suddenly? Is there anything I can do to fix it?
I'm using Azure Hosted builds
I have managed to solve this.
It appears that the issue occurs because the build process uses something called node_gyp. Apparently this stopped working after node 11.x and node 12 is now the default node that Azure DevOps is using (or is at the time of writing).
I was able to rectify the problem by adding a build step to the Pipeline to install node 8.x - After that all worked fine.
Looks like upgrading node-sass should also fix it (but wary of this given the age of the project so not an ideal solution)...
https://github.com/nodejs/node-gyp/issues/1763 (link for additional info on underlying node-gyp compatibility problems)

install4j Windows Edition 7.0.9 - an error in Install file step

install4j Windows Edition 7.0.9(build7273)
I run the exe file and get an error from "Install files" step
this step copy my files to $ folder (temporary folder)
Install file: D:\RT.Server.Service.Pack.7.1.1\$\rtserver.install4j\i4jinst.dll; size: 171008 bytes; exists: false
[ERROR] com.install4j.runtime.beans.actions.InstallFilesAction [ID 53416]: java.io.IOException: The filename, directory name, or volume label syntax is incorrect
java.io.IOException: The filename, directory name, or volume label syntax is incorrect
at java.io.WinNTFileSystem.canonicalize0(Native Method)
at java.io.WinNTFileSystem.canonicalize(WinNTFileSystem.java:428)
windows server2012 R2
-
-

Cannot start GlassFish in Eclipse: GlassFish error : Could not find or load main class files

I am attempting to start glassfish from within eclipse (juno). I get the following error:
INFO: Successfully launched in 10 msec.
Error: Could not find or load main class Files
Command start-domain failed.
The DAS was stopped.
Here is the complete output in Eclipse:
Aug 16, 2012 11:51:23 AM com.sun.enterprise.admin.launcher.GFLauncherLogger info
INFO: JVM invocation command line:
C:\Program Files\Java\jdk1.7.0\bin\java.exe
-cp
C:/glassfish3-2/glassfish3/glassfish/modules/glassfish.jar
-XX:+UnlockDiagnosticVMOptions
-XX:MaxPermSize=192m
-XX:NewRatio=2
-Xmx512m
-javaagent:C:/glassfish3-2/glassfish3/glassfish/lib/monitor/btrace- agent.jar=unsafe=true,noServer=true
-client
-Dosgi.shell.telnet.maxconn=1
-Dfelix.fileinstall.disableConfigSave=false
-Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
-Dfelix.fileinstall.dir=C:\glassfish3-2\glassfish3\glassfish/modules/autostart/
-Djavax.net.ssl.keyStore=C:\glassfish3-2\glassfish3\glassfish\domains\domain1/config/keystore.jks
-Dosgi.shell.telnet.port=6666
-Djava.security.policy=C:\glassfish3-2\glassfish3\glassfish\domains\domain1/config/server.policy
-Dfelix.fileinstall.log.level=2
-Dfelix.fileinstall.poll=5000
-Dcom.sun.aas.instanceRoot=C:\glassfish3-2\glassfish3\glassfish\domains\domain1
-Dosgi.shell.telnet.ip=127.0.0.1
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serv erbeans.AppserverConfigEnvironmentFactory
-Djava.endorsed.dirs=C:\glassfish3-2\glassfish3\glassfish/modules/endorsed; C:\glassfish3-2\glassfish3\glassfish/lib/endorsed
-Dcom.sun.aas.installRoot=C:\glassfish3-2\glassfish3\glassfish
-Dfelix.fileinstall.bundles.startTransient=true
-Djava.ext.dirs=C:\Program Files\Java\jdk1.7.0/lib/ext;C:\Program Files\Java\jdk1.7.0/jre/lib/ext;C:\glassfish3-2\glassfish3\glassfish\domains\domain1/lib/ext
-Dfelix.fileinstall.bundles.new.start=true
-Djavax.net.ssl.trustStore=C:\glassfish3-2\glassfish3\glassfish\domains\domain1/config/cacerts.jks
Dorg.glassfish.additionalOSGiBundlesToStart=org.apache.felix.shell,org.apache.felix.gogo.runtime,org.apache.felix.gogo.shell,org.apache.felix.gogo.command
-Dcom.sun.enterprise.security.httpsOutboundKeyAlias=s1as
-Djava.security.auth.login.config=C:\glassfish3-2\glassfish3\glassfish\domains\domain1/config/login.conf
-DANTLR_USE_DIRECT_CLASS_LOADING=true
-Dgosh.args=--nointeractive
-Djava.library.path=C:/glassfish3-2/glassfish3/glassfish/lib;C:/Program Files/Java/jdk1.7.0/bin;C:/Windows/Sun/Java/bin;C:/Windows/System32;C:/Windows;C:/Program Files (x86)/HP SimplePass 2011/x64;C:/Program Files (x86)/HP SimplePass 2011;C:/Program Files/Common Files/Microsoft Shared/Windows Live;C:/Program Files (x86)/Common Files/microsoft shared/Windows Live;C:/Windows/System32/wbem;C:/Windows/System32/WindowsPowerShell/v1.0;C:/Program Files (x86)/Windows Live/Shared;C:/Program Files/Intel/WiFi/bin;C:/Program Files/Common Files/Intel/WirelessCommon;C:/Program Files (x86)/Intel/Services/IPT;C:/Program Files (x86)/Microsoft SQL Server/100/Tools/Binn;C:/Program Files/Microsoft SQL Server/100/Tools/Binn;C:/Program Files/Microsoft SQL Server/100/DTS/Binn;C:/Program Files (x86)/Microsoft ASP.NET/ASP.NET Web Pages/v1.0;C:/Program Files (x86)/Java/jdk1.7.0_01/bin;C:/glassfish3-2/glassfish3/glassfish/"C:/eclipse/eclipse.exe;C:/glassfish3-2/glassfish3/glassfish/" -vm "C:/Program Files (x86)/Java/jdk1.7.0_01/jre/bin/javaw.exe;C:/glassfish3-2/glassfish3/glassfish/.;C:/Program Files/Microsoft SQL Server/110/Tools/Binn;C:/Program Files (x86)/Microsoft SQL Server/110/Tools/Binn;C:/Program Files/Microsoft SQL Server/110/DTS/Binn;C:/Program Files (x86)/Microsoft SQL Server/110/Tools/Binn/ManagementStudio;C:/Program Files (x86)/Microsoft SQL Server/110/DTS/Binn;C:/Program Files/jEdit;C:/Program Files (x86)/Java/jre7/bin;C:/Program Files (x86)/QuickTime/QTSystem;C:/Program Files/Java/jdk1.7.0/db/bin;C:/glassfish3-2/glassfish3/glassfish
com.sun.enterprise.glassfish.bootstrap.ASMain
-domainname
domain1
-asadmin-args
host,,,localhost,,,--port,,,4848,,,--secure=false,,,--terse=false,,,--echo=false,,,--interactive=false,,,start-domain,,,--verbose=true,,,--debug=false,,,--domaindir,,,C:\glassfish3-2\glassfish3\glassfish\domains,,,domain1
-instancename
server
-verbose
true
-debug
false
-asadmin-classpath
C:/glassfish3-2/glassfish3/glassfish/modules/admin-cli.jar
-asadmin-classname
com.sun.enterprise.admin.cli.AsadminMain
-upgrade
false
-type
DAS
-domaindir
C:/glassfish3-2/glassfish3/glassfish/domains/domain1
-read-stdin
true
Aug 16, 2012 11:51:23 AM com.sun.enterprise.admin.launcher.GFLauncherLogger info
INFO: Successfully launched in 10 msec.
Error: Could not find or load main class Files
Command start-domain failed.
The DAS was stopped.
Thanks as always in advance.
Regards,
umbregachoong
This happened to me with glassfish started on command prompt.
c:\glassfish4\glassfish\bin>asadmin start-domain
Waiting for domain1 to start .
Error starting domain domain1.
The server exited prematurely with exit code 1.
Before it died, it produced the following output:
Error: Could not find or load main class Files
Command start-domain failed.
It was caused by having the following on PATH:
Path=...;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;...
I had the same issue as jan.supol, setting the path of the NVIDIA binaries into double-quotes like this also fixed it for me:
Path=...;"C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common";...
Most probably this can be caused by any whitespace in the PATH-variable that is not enclosed in double-quotes.

Hadoop on windows with eclipse

I read a post here on stack overflow about this link being very good for hadoop deployment on windows - http://v-lad.org/Tutorials/Hadoop/12%20-%20format%20the%20namendoe.html
Problem is when I format the namenode as given on that page, after
bin/hadoop namenode -format
I get the following error:
Maybe its a problem with my environmental variables but I'm not sure.
bin/hadoop: line 330: C:\Program: command not found
bin/hadoop: line 395: C:\Program Files\java\jdk1.7.0\bin/bin/java: No such
file/directory
bin/hadoop: line 395: exec: C:\Program Files\java\jdk1.7.0\bin/bin/java: cannot
execute: No such file or directory
Just set you JAVA_HOME properly, it resolved my issue-
anwar#dell-pc ~/hadoop-0.20.203.0
$ export JAVA_HOME="C:\Program Files\Java\jdk1.6.0_02"