When executing PlasticSCM-5.4.16.628-osx-installer.app on OS X 10.10.1 (Yosemite), the password is requested and entered, nothing else appears on the screen.
Checking the console reveals Service exited with abnormal code: 129
The system has PlasticSCM version 5.0.44.581 - Manaos, originally installed under OS X 10.6.8 (Snow Leopard), prior to the Yosemite upgrade. Plastic Manaos is running as expected, under Yosemite after upgrading X11 to XQuartz 2.7.7.
The full log entries for the failed installer execution:
12/9/14 6:41:35.782 PM SecurityAgent[4423]: Failed to initialize IconCache named: com.apple.iconservices with error: Error Domain=NSCocoaErrorDomain Code=4097 "Couldn’t communicate with a helper application." (connection to service named com.apple.iconservices) UserInfo=0x7ffcb3da95c0 {NSDebugDescription=connection to service named com.apple.iconservices}
12/9/14 6:41:35.783 PM SecurityAgent[4423]: Error returned from iconservicesagent: Error Domain=NSCocoaErrorDomain Code=4097 "Couldn’t communicate with a helper application." (connection to service named com.apple.iconservices) UserInfo=0x7ffcb3dacc00 {NSDebugDescription=connection to service named com.apple.iconservices}
12/9/14 6:41:42.822 PM SecurityAgent[4423]: Error returned from iconservicesagent: Error Domain=NSCocoaErrorDomain Code=4097 "Couldn’t communicate with a helper application." (connection to service named com.apple.iconservices) UserInfo=0x7ffcb3c99b50 {NSDebugDescription=connection to service named com.apple.iconservices}
12/9/14 6:41:43.043 PM authexec[4427]: executing /Users/glen/Downloads/PlasticSCM-5.4.16.628-osx-installer.app/Contents/MacOS/osx-intel
12/9/14 6:41:43.047 PM com.apple.xpc.launchd[1]: (com.bitrock.appinstaller.194004[4414]) Service exited with abnormal code: 129
I've googled a few phrases from the above, but still need a clue as to how to begin troubleshooting.
Any further ideas are much appreciated.
The problem is that the installer, osx-intel is not flagged as executable. Also sudo privileges are required.
From terminal, same directory as installer:
$ chmod +x ./PlasticSCM-5.4.16.633-osx-installer.app/Contents/MacOS/osx-intel
$ sudo ./PlasticSCM-5.4.16.633-osx-installer.app/Contents/MacOS/osx-intel
Success!
Related
I have a macos app with a pkg installer. The pkg has a postinstall.sh and a preinstall.sh.
On most machines it works fine but for certain customers I get reports that the script has failed.
I've asked the users to send me the installer logs but those don't contain the actual bash error only something like this:
Sep 14 15:04:16 Filestars-Mac-Mini installd[2540]: PackageKit: Install Failed: Error Domain=PKInstallErrorDomain Code=112 "An error occurred while running scripts from the package “Filestar.21.0.12.0.osx-x64.pkg”." UserInfo={NSFilePath=./preinstall, NSURL=file:///Users/filestar/repos/Filestar/Filestar.Installer/macOs/Output/Filestar.21.0.12.0.osx-x64.pkg#Filestar.pkg, PKInstallPackageIdentifier=com.Filestar.pkg.Filestar, NSLocalizedDescription=An error occurred while running scripts from the package “Filestar.21.0.12.0.osx-x64.pkg”.} {
NSFilePath = "./preinstall";
NSLocalizedDescription = "An error occurred while running scripts from the package \U201cFilestar.21.0.12.0.osx-x64.pkg\U201d.";
NSURL = "file:///Users/filestar/repos/Filestar/Filestar.Installer/macOs/Output/Filestar.21.0.12.0.osx-x64.pkg#Filestar.pkg";
PKInstallPackageIdentifier = "com.Filestar.pkg.Filestar";
}
How can I get the actual error?
During your preinstall.sh and postinstall.sh scripts, append to a log file. For example, you can rm -rf /var/tmp/Filestar.log during preinstall.sh then append anything you deem interesting there. Doing the same for postinstall.sh. Then if the user reports an issue have them send you the log file.
I have a blocking issue installing openwhisk with docker
I typed make quick-start right after a git pull of the project incubator-openwhisk-devtools. My OS is Fedora 29, docker version is 18.09.0, docker-compose version is 1.22.0. JDk 8 Oracle.
I get the following error:
[...]
adding the function to whisk ...
ok: created action hello
invoking the function ...
error: Unable to invoke action 'hello': The server is currently unavailable (because it is overloaded or down for maintenance). (code ciOZDS8VySDyVuETF14n8QqB9wifUboT)
[...]
[ERROR] [#tid_sid_unknown] [Invoker] failed to ping the controller: org.apache.kafka.common.errors.TimeoutException: Expiring 1 record(s) for health-0: 30069 ms has passed since batch creation plus linger time
[ERROR] [#tid_sid_unknown] [KafkaProducerConnector] sending message on topic 'health' failed: Expiring 1 record(s) for health-0: 30009 ms has passed since batch creation plus linger time
Please note that controller-local-logs.log is never created.
If I issue a touch controller-local-logs.log in the right directory the log file is always empty after I try to issue make quick-start again.
http://localhost:8888/ping gives me the right answer: pong.
http://localhost:9222 is not reacheable.
Where am I wrong?
Thank you in advance
I am attempting to install Oracle HTTP server 12.2.1.1 on Windows Server 2012 R2 in standalone mode. I believe I followed the Oracle documentation correctly. I have progressed to this point: https://docs.oracle.com/middleware/1221/core/WTINS/GUID-3ED8EE64-EE8B-4EF3-84A1-19CEF21B8547.htm#WTINS414
My attempts to run "startComponent.cmd ohs1" have resulted in this error:
weblogic.nodemanager.NMException: Received error message from Node Manager Serve
r: [Server start command for OHS server 'ohs1' failed due to: [Failed t
o start the server ohs1
The error message also says to check a log file. Contents are:
<2016-06-29 15:42:10> <INFO> <OHS-4018> <Starting server ohs1>
<2016-06-29 15:42:10> <INFO> <OHS-0> <Running C:\Middleware\Oracle_Home_12\ohs\bin\launch.exe C:\Middleware\Oracle_Home_12\ohs\bin\httpd.exe -DOHS_MPM_WINNT -d C:/Middleware/Oracle_Home_12/user_projects/domains/base_domain/config/fmwconfig/components/OHS/instances/ohs1 -f C:\Middleware\Oracle_Home_12\user_projects\domains\base_domain\config\fmwconfig\components\OHS\instances\ohs1\httpd.conf>
<2016-06-29 15:42:11> <SEVERE> <OHS-0> <C:\Middleware\Oracle_Home_12\ohs\bin\launch.exe C:\Middleware\Oracle_Home_12\ohs\bin\httpd.exe -DOHS_MPM_WINNT -d C:/Middleware/Oracle_Home_12/user_projects/domains/base_domain/config/fmwconfig/components/OHS/instances/ohs1 -f C:\Middleware\Oracle_Home_12\user_projects\domains\base_domain\config\fmwconfig\components\OHS\instances\ohs1\httpd.conf: exit status = -1073741515>
<2016-06-29 15:42:11> <INFO> <OHS-4005> <Check the instance log file for more information: C:\Middleware\Oracle_Home_12\user_projects\domains\base_domain\servers\ohs1\logs\ohs1.log>
<2016-06-29 15:42:11> <SEVERE> <OHS-0> <Failed to start the server ohs1>
The log file referenced here, "C:\Middleware\Oracle_Home_12\user_projects\domains\base_domain\servers\ohs1\logs\ohs1.log", does not exist.
I also made sure that the required Microsoft redistributable was installed.
What am I doing wrong?
I received help from the Oracle Community:
Do you have lastinvocation.log file under
C:/Middleware/Oracle_Home_12/user_projects/domains\base_domain\servers\ohs1\logs?
If yes, rename it to lastinvocation.cmd and run this from command line and check if the ohs1.log file gets generated.
If yes, what is the error message seen?
The error message returned was:
"The program can't start because MSVCR110.dll is missing from your computer. Try reinstalling the program to fix this problem."
The user then pointed me to an Oracle Doc:
This is also described in the below article
Oracle HTTP Server 12.2.1 Fails To Start With Error 'MSVCR110.dll' Missing From Your Computer (Doc ID 2078713.1)
This Oracle article had a link to a DIFFERENT (larger) version of vcredist_x64.exe than I had used when installing the components. This version worked.
Thanks to Aishwarya in the Oracle community!
I've installed sencha cmd on mac os x 10.7.5. When I try to start the web server with the command: "sencha web start" I receive the following error message:
[...]
14:28:03.274 [main] ERROR com.sencha.command.Sencha - org.slf4j.helpers.MessageFormatter.arrayFormat(Ljava/lang/String;[Ljava/lang/Object;)Lorg/slf4j/helpers/FormattingTuple;
at com.sencha.exceptions.BasicException.wrap(BasicException.java:51)
at com.sencha.exceptions.BasicException.stealthify(BasicException.java:43)
at com.sencha.exceptions.BasicException.raise(BasicException.java:35)
at com.sencha.cli.Command.dispatch(Command.java:64)
at com.sencha.cli.Commands.dispatch(Commands.java:64)
at com.sencha.cli.Commands.dispatch(Commands.java:64)
at com.sencha.command.Sencha.dispatch(Sencha.java:80)
at com.sencha.command.Sencha.main(Sencha.java:148)
[...]
Is anyone has some idea what can be wrong ? I've tried both sencha cmd versions 5.0.0 and 4.0.4...and the error message is always the same. I'm absolutely beginner in sencha so maybe Im doing something completely wrong
I am building a simple package on OS X using pkgbuild that consists of a folder of stuff and the pre/postinstall scripts. When I try to execute the resulting package, the installer fails with the following message in the log:
Nov 1 13:28:11 localhost installd[631]: ./preinstall: 2013-11-01 13:28:11.074 installd[637:203] * NSTask: Task create for path '/tmp/PKInstallSandbox.P6mPx2/Scripts/com.xyz.utility.pkg.TWwYct/preinstall' failed: 22, "Invalid argument". Terminating temporary process.
The installer is running as root. The problem does not appear to be the contents of the scripts since they fail even after I cut them down to a simple "exit 0" with the interpreter declaration. This issues occurs on 10.8.2 and 10.8.4.
The issue looks like an exception that is thrown from within an NSTask object, but all I get is this 22 error code and the "Invalid argument" message. I think this message might refer to an NSInvalidArgumentException. I made sure the scripts are indeed being placed at the temporary location listed in the error message and they are there with the correct permissions.
Any ideas as to what causes this type of error message? I found several references to this error when I did some searching but there didn't seem to be a unifying cause or solution.
Add #!/bin/sh header into the preinstall script.