Execution error : file 'rm1p0018' error code: 114, pc=0, call=1, seg=0 114 Attempt to access item beyond bounds of memory (Signal 11) - procobol

When I ran a script on HP-UX server then I am getting below error. Script is calling one executable file( rm1p0018 ) which made by cobol file.
Here is the error message from the log:
Execution error : file 'rm1p0018'
error code: 114, pc=0, call=1, seg=0
114 Attempt to access item beyond bounds of memory (Signal 11)
HP/MF COBOL Version: B.13.50
HP-UX df2hp405 B.11.11 U 9000/800
pid: 12766 gid: 20 uid: 9831
Wed Aug 8 08:52:19 2012
8:52am up 2 days, 11:04, 4 users, load average: 0.01, 0.01, 0.01
Thread mode: No Threads
RTS Error: COBOL
Sync Signals: COBOL
ASync Signals: COBOL
cobtidy on exception: False
Recently oracle database was migrated from HP-UX to AIX server with the upgraded version of 10g from 9i.
Intially application and DB both were resides on HP-UX server but now application is resides on HP-UX and DB is resides on AIX server.
Can someone help me out on this issue.

A little bit hard to guess the cause of this memory violation.
If you are able to recompile the Cobol program, I advice you to trace it using "ready trace." statement along with $set trace directive.
You will be able then to have a trace of all cobol paragraphs executed and deduce the one where the program stopped and raised the error.

Related

What does "Failed to execute /init (error -7)" mean?

Linux kernel version: 4.18.0-17
I am porting some 4.15 kernel customizations to 4.18, but my 4.18 kernel does not boot. A stock 4.18 kernel (i.e. the starting point before merging the 4.15 modifications) boots and runs.
The error message is:
Failed to execute /init (error -7)
Starting init: /bin/sh exists but couldn't execute it (error -7)
"errno 7" is "E2BIG 7 Argument list too long"
What does that mean in the context of the kernel starting the init process?
If the kernel command line and root file systems is exactly the same as the one you are giving to the kernel version that does boot than the most likely cause is that get_user_pages_remote() is failing here: https://elixir.bootlin.com/linux/v4.18/source/fs/exec.c#L194
Which would imply one of your changes broke memory management.
To get here, just track from try_to_run_init_process() which runs init to all the functions called from it which can return E2BIG. This is the only call site that does not depend on init argument list or environment size - https://elixir.bootlin.com/linux/v4.18/source/init/main.c#L1001
Having said that, I would first make VERY sure that the kernel command line and root file system are the same.

Lighttpd closes connection when system time is changed

These are some of the parameters of my lighttpd config file.
server.modules += ( "mod_wstunnel", "mod_auth")
wstunnel.debug = 4
wstunnel.server.max-read-idle = 86400
#wstunnel.ping-interval = 5
#wstunnel.timeout = 30
When I open my web application, connection is created properly using websocket and connects to my c++ server.
All functionalities work except one.
One requirement of my application is to change the system time of machine, but when system time is changed, connection is closed and in log file it shows as :
`2019-02-12 14:04:10: (gw_backend.c.308) released proc: pid: 0 socket: tcp:127.0.0.1:10002 load: 0`
I want to maintain the connection even if system time is changed.
What other parameters can be used or any modification is required in these parameters?
System OS : Fedora 26
Lighttpd version : 1.4.49
wstunnel.server.max-read-idle does not exist. Did you test the lighttpd config before running it and look at the error trace? It should have noted wstunnel.server.max-read-idle as an unrecognized directive.
The directives you seek are:
server.max-read-idle
server.max-write-idle
server.max-keep-alive-idle
However, if the time on your server (running lighttpd) is jumping more than a few seconds, then I suggest that is your primary problem.
Also, Fedora 26 reach end-of-life on May 29, 2018. Supported Fedora have newer version of lighttpd. The current version of lighttpd is lighttpd 1.4.53.

unable to init h2o. can somebody help me with it

Checking whether there is an H2O instance running at http://localhost:54321..... not found.
Attempting to start a local H2O server...
Java HotSpot(TM) 64-Bit Server VM (build 9.0.1+11, mixed mode)
Starting server from
C:\Users\Ramakanth\Anaconda2\lib\site-packages\h2o\backend\bin\h2o.jar
Ice root: c:\users\ramaka~1\appdata\local\temp\tmpeaff8n JVM stdout:
c:\users\ramaka~1\appdata\local\temp\tmpeaff8n\h2o_Ramakanth_started_from_python.out
JVM stderr:
c:\users\ramaka~1\appdata\local\temp\tmpeaff8n\h2o_Ramakanth_started_from_python.err
Traceback (most recent call last): File "", line 1, in
File
"C:\Users\Ramakanth\Anaconda2\lib\site-packages\h2o\h2o.py", line 262,
in init
min_mem_size=mmin, ice_root=ice_root, port=port, extra_classpath=extra_classpath) File
"C:\Users\Ramakanth\Anaconda2\lib\site-packages\h2o\backend\server.py",
line 121, in start
mmax=max_mem_size, mmin=min_mem_size) File "C:\Users\Ramakanth\Anaconda2\lib\site-packages\h2o\backend\server.py",
line 317, in _launch_server
raise H2OServerError("Server process terminated with error code %d" % proc.returncode) h2o.exceptions.H2OServerError: Server process
terminated with error code 1
Assuming "build 9.0.1+11" means Java 9, that is your problem: H2O currently only supports Java 7 or Java 8. This is the ticket to follow for adding Java 9 support. In the meantime uninstall your current Java, then install Java 8.
UPDATE: It seems Java 9 is now supported, so upgrade to h2o 3.20 or later.
BTW, normally you should be giving a lot more information: which language you are using, what code you used to try and start H2O (or the commandline if you started it that way), what OS, what versions of Java, R, Python, etc., number of cores, amount of memory, etc.

"Symbol not found" error, (possibly) due to recent upgrade to R2017b?

I'm getting an error when I try to use imerode() from the command line, e.g.
test=magic([100 100])>200;
imclose(test,strel('disk',10,0));
I get this error:
Error using images.internal.morphmex Invalid MEX-file
'/Applications/MATLAB_R2017b.app/toolbox/images/images/+images/+internal/morphmex.mexmaci64':
dlopen(/Applications/MATLAB_R2017b.app/toolbox/images/images/+images/+internal/morphmex.mexmaci64,
6): Symbol not found: _OSAtomicDecrement32Barrier Referenced from:
/Applications/MATLAB_R2017b.app/bin/maci64/./libcudart.8.0.dylib
Expected in: /usr/lib/libSystem.B.dylib in
/Applications/MATLAB_R2017b.app/bin/maci64/./libcudart.8.0.dylib.
Error in images.internal.morphop (line 103)
B = images.internal.morphmex(mex_method, B, nhood, height, unpacked_M);
Error in imdilate (line 135) B =
images.internal.morphop(A,se,'dilate',mfilename,varargin{:});
Error in imclose (line 82)
outputImage = imerode(imdilate(inputImage,se,packopt,M),se,packopt,M);
I'm on OS X 10.9.5, with MATLAB R2017b.
I've checked that morphmex.mexmaci64 is there in the given path (above).
Not sure where /./ refers to, but libcudart.8.0.dylib is in maci64 folder.
Not sure where /usr/lib/... is.
EDIT
I have uninstalled R2017b and installed R2017a (why not, just in case...) and when trying to run the same code, I now get this error (which seems worse...)
Segmentation violation detected at Mon Nov 13 13:44:29 2017
Configuration: Crash Decoding : Disabled - No sandbox or build
area path Crash Mode : continue (default) Current
Graphics Driver: Unknown hardware Current Visual : Quartz
Default Encoding : ISO-8859-1 Deployed : false Host
Name : eduroam-206-52.nomadic.bris.ac.uk MATLAB
Architecture : maci64 MATLAB Entitlement ID: 1803495 MATLAB Root
: /Applications/MATLAB_R2017a.app MATLAB Version : 9.2.0.556344
(R2017a) OpenGL : hardware Operating System :
Darwin 13.4.0 Darwin Kernel Version 13.4.0: Mon Jan 11 18:17:34 PST
2016; root:xnu-2422.115.15~1/RELEASE_X86_64 x86_64 Processor ID
: x86 Family 6 Model 69 Stepping 1, GenuineIntel Virtual Machine
: Java 1.7.0_75-b13 with Oracle Corporation Java HotSpot(TM) 64-Bit
Server VM mixed mode Window System : Quartz
Fault Count: 2
Abnormal termination: Trace trap
Can upload error file for rest of message (too long to paste here).
Thanks in advance.
Looks like an installation problem or maybe it is due to the update.
Try to run the following commands in your console:
restoredefaultpath();
rehash toolboxcache;
If everything works without errors, then run:
savepath();
Turns out R2017a, b not compatible with OS Mavericks.
Rolled back to R2016a.

Help deciphering this Fatal Error (Java)

A fatal error has been detected by the Java Runtime Environment:
EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x762a76d0, pid=4072, tid=2984
JRE version: 6.0_26-b03
Java VM: Java HotSpot(TM) Client VM (20.1-b02 mixed mode, sharing windows-x86 )
Problematic frame:
C [ole32.dll+0x376d0]
Error Log: http://pastebin.com/zpBst6W1
Line 3 says your program failed in the AWT-EventQueue-0 thread, also called the event dispatch thread (EDT). The execution stack trace starts in line 111, and builds up. At line 47, in the package sun.awt.windows and class WComponentPeer, the method addNativeDropTarget() attempted to call into the shared library, ole32.dll, failing at entry CoUnmarshalInterface. The rest describes the processor state at the time.
This can happen if the shared library is not the one expected by the Java Runtime Environment (JRE). You may need to check your installation.
This is a known bug in Java 6 that is still open:
http://bugs.java.com/bugdatabase/view_bug.do;jsessionid=e5f1f1011daf96ffffffffdd154dd2e731150?bug_id=6967456
https://bugs.openjdk.java.net/browse/JDK-6967456?page=com.atlassian.jira.plugin.system.issuetabpanels:changehistory-tabpanel

Resources