dbTalk Databases Forums  

D3/Linux 7.5.0 printer error

comp.databases.pick comp.databases.pick


Discuss D3/Linux 7.5.0 printer error in the comp.databases.pick forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
mwright
 
Posts: n/a

Default D3/Linux 7.5.0 printer error - 05-14-2007 , 03:56 PM






We're playing around with the above prior to going live with it, & are
getting an error when shutting down the D3 process. The error message
is as follows:

lppick: sigsegv

It occurs for each networked printer we have set up on the system. So
far, these printers seem to function normally, & the error only occurs
when we do a shutdown of the pick machine. I've searched CDP & can
find nothing on this particular error message.

Does anyone have a clue as to what might be going on?? Is it
something worth worrying over??

BTW, we're using CUPS printing on the linux side. Haven't tried any
of the other options on this particular platform.

Mark Wright
Eastex Crude Company


Reply With Quote
  #2  
Old   
john@mrpsystems.co.uk
 
Posts: n/a

Default Re: D3/Linux 7.5.0 printer error - 05-15-2007 , 02:25 AM






Hello Mark

Just a few questions first?

How are the printers set-up in CUPS?

Are you using CUPS-LPD?

What is your startshp comnmand look like?

Regards

John


Reply With Quote
  #3  
Old   
jra
 
Posts: n/a

Default Re: D3/Linux 7.5.0 printer error - 05-15-2007 , 01:50 PM



This where in RD forums by Robert Burke

"Changes that were made to dm,devices, lp.unix required a recompile of
the devices item."
"You need to assign to a form.queue using lp.unix then add the (c
option to compile. Example:

assignfq 2,lp.unix (c

"

Hope this help
joseba


On 14 mayo, 22:56, mwright <wright.m... (AT) gmail (DOT) com> wrote:
Quote:
We're playing around with the above prior to going live with it, & are
getting an error when shutting down the D3 process. The error message
is as follows:

lppick: sigsegv

It occurs for each networked printer we have set up on the system. So
far, these printers seem to function normally, & the error only occurs
when we do a shutdown of the pick machine. I've searched CDP & can
find nothing on this particular error message.

Does anyone have a clue as to what might be going on?? Is it
something worth worrying over??

BTW, we're using CUPS printing on the linux side. Haven't tried any
of the other options on this particular platform.

Mark Wright
Eastex Crude Company



Reply With Quote
  #4  
Old   
mwright
 
Posts: n/a

Default Re: D3/Linux 7.5.0 printer error - 05-21-2007 , 01:01 PM



On May 15, 2:25 am, j... (AT) mrpsystems (DOT) co.uk wrote:
John,

The printers in question are set up as Networked Windows (smb)
printers in linux (CUPS). Yes, we ARE using CUPS-LPD.

Our startshp commands are similar to this:

startshp 7,81,1,s36,lp.unix,(lpr -Pmark) (s

Let me know what you think.

MW

Quote:
Hello Mark

Just a few questions first?

How are the printers set-up in CUPS?

Are you using CUPS-LPD?

What is your startshp comnmand look like?

Regards

John



Reply With Quote
  #5  
Old   
mwright
 
Posts: n/a

Default Re: D3/Linux 7.5.0 printer error - 05-21-2007 , 01:02 PM



On May 15, 1:50 pm, jra <jrajos... (AT) gmail (DOT) com> wrote:
Joseba,

We tried this, with no luck. :^( Still getting the same message upon
shutdown.

MW

Quote:
This where in RD forums by Robert Burke

"Changes that were made to dm,devices, lp.unix required a recompile of
the devices item."
"You need to assign to a form.queue using lp.unix then add the (c
option to compile. Example:

assignfq 2,lp.unix (c

"

Hope this help
joseba

On 14 mayo, 22:56, mwright <wright.m... (AT) gmail (DOT) com> wrote:

We're playing around with the above prior to going live with it, & are
getting an error when shutting down the D3 process. The error message
is as follows:

lppick: sigsegv

It occurs for each networked printer we have set up on the system. So
far, these printers seem to function normally, & the error only occurs
when we do a shutdown of the pick machine. I've searched CDP & can
find nothing on this particular error message.

Does anyone have a clue as to what might be going on?? Is it
something worth worrying over??

BTW, we're using CUPS printing on the linux side. Haven't tried any
of the other options on this particular platform.

Mark Wright
Eastex Crude Company



Reply With Quote
  #6  
Old   
john@mrpsystems.co.uk
 
Posts: n/a

Default Re: D3/Linux 7.5.0 printer error - 05-22-2007 , 07:47 AM



What version of D3-Linix you using?

and patches?

I have just got the SAME error message on my D3-Linux 7.5.0
development box.

i will meail this link to RD Support also. !!!

John



Reply With Quote
  #7  
Old   
john@mrpsystems.co.uk
 
Posts: n/a

Default Re: D3/Linux 7.5.0 printer error - 05-22-2007 , 08:13 AM



Hello Mark

RD have an out/s action item on it already,

John


Reply With Quote
  #8  
Old   
mwright
 
Posts: n/a

Default Re: D3/Linux 7.5.0 printer error - 05-22-2007 , 08:55 AM



John,

We're using 7.5.0, with no installed patches.

Please let me know if you hear anything meaningful.

MW

On May 22, 7:47 am, j... (AT) mrpsystems (DOT) co.uk wrote:
Quote:
What version of D3-Linix you using?

and patches?

I have just got the SAME error message on my D3-Linux 7.5.0
development box.

i will meail this link to RD Support also. !!!

John



Reply With Quote
  #9  
Old   
mwright
 
Posts: n/a

Default Re: D3/Linux 7.5.0 printer error - 05-22-2007 , 11:30 AM



John,

We're using 7.5.0, with no installed patches.

Please let me know if you hear anything meaningful.

MW

On May 22, 7:47 am, j... (AT) mrpsystems (DOT) co.uk wrote:
Quote:
What version of D3-Linix you using?

and patches?

I have just got the SAME error message on my D3-Linux 7.5.0
development box.

i will meail this link to RD Support also. !!!

John



Reply With Quote
  #10  
Old   
richard.ottinger@eastexcrude.com
 
Posts: n/a

Default Re: D3/Linux 7.5.0 printer error - 05-23-2007 , 09:36 AM



On May 22, 1:27 pm, "Glen B" <no$pamwebmaster@no$pamforallspec.com>
wrote:
Quote:
sigsegv is a signal which notes that the process has made invalid
memory references. lppick is being a bad little program. I'm sure an strace
would point out the bug. Try starting one shared printer at boot-up, kill
the lppick process manually after D3 starts and then start lppick manually
from another shell with strace. If you do "!ps ax | grep lppick" from TCL
you can see the lppick command line. You should be able to catch the memory
exception lppick is throwing. Copy and paste the last screen or so of the
strace log here or in the RD support forum.

Glen

"mwright" <wright.m... (AT) gmail (DOT) com> wrote in message

news:1179176168.322785.48980 (AT) k79g2000hse (DOT) googlegroups.com...

We're playing around with the above prior to going live with it, & are
getting an error when shutting down the D3 process. The error message
is as follows:

lppick: sigsegv

It occurs for each networked printer we have set up on the system. So
far, these printers seem to function normally, & the error only occurs
when we do a shutdown of the pick machine. I've searched CDP & can
find nothing on this particular error message.

Does anyone have a clue as to what might be going on?? Is it
something worth worrying over??

BTW, we're using CUPS printing on the linux side. Haven't tried any
of the other options on this particular platform.

Mark Wright
Eastex Crude Company
Glen,
I killed lppick & restarted it using strace & got the following output
when I first ran it...

[root@d3test ~]# strace lppick -l /var/tmp/lppick/pick0_7_36 -s End of
Job -c exec lpr -Pmark
execve("/usr/bin/lppick", ["lppick", "-l", "/var/tmp/lppick/
pick0_7_36", "-s", "End", "of", "Job", "-c", "exec", "lpr", "-Pmark"],
[/* 32 vars */]) = 0
uname({sys="Linux", node="d3test", ...}) = 0
brk(0) = 0x9ed6000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=50699, ...}) = 0
old_mmap(NULL, 50699, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7ff3000
close(3) = 0
open("/lib/tls/libc.so.6", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0 \0 O=\000"...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=1454835, ...}) = 0
old_mmap(0x3c0000, 1215644, PROT_READ|PROT_EXEC, MAP_PRIVATE|
MAP_DENYWRITE, 3, 0) = 0x3c0000
old_mmap(0x4e3000, 16384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|
MAP_DENYWRITE, 3, 0x123000) = 0x4e3000
old_mmap(0x4e7000, 7324, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|
MAP_ANONYMOUS, -1, 0) = 0x4e7000
close(3) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0) = 0xb7ff2000
mprotect(0x4e3000, 4096, PROT_READ) = 0
mprotect(0x3bc000, 4096, PROT_READ) = 0
set_thread_area({entry_number:-1 -> 6, base_addr:0xb7ff2aa0, limit:
1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1,
seg_not_present:0, useable:1}) = 0
munmap(0xb7ff3000, 50699) = 0
brk(0) = 0x9ed6000
brk(0x9ef7000) = 0x9ef7000
open("/etc/localtime", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=1267, ...}) = 0
fstat64(3, {st_mode=S_IFREG|0644, st_size=1267, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xb7fff000
read(3, "TZif\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\4\0\0\ 0\4\0"...,
4096) = 1267
close(3) = 0
munmap(0xb7fff000, 4096) = 0
setpgid(0, 0) = 0
rt_sigaction(SIGHUP, {SIG_IGN}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGINT, {SIG_IGN}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGQUIT, {SIG_IGN}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGALRM, {SIG_IGN}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGUSR1, {SIG_IGN}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGUSR2, {SIG_IGN}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGTERM, {0x8048894, [TERM], SA_RESTORER|SA_RESTART,
0x3e7a48}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGILL, {0x80488c9, [ILL], SA_RESTORER|SA_RESTART,
0x3e7a48}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGBUS, {0x80488f5, [BUS], SA_RESTORER|SA_RESTART,
0x3e7a48}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGPWR, {0x8048921, [PWR], SA_RESTORER|SA_RESTART,
0x3e7a48}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGSEGV, {0x8048956, [SEGV], SA_RESTORER|SA_RESTART,
0x3e7a48}, {SIG_DFL}, 8) = 0
getpid() = 24894


when I kill lppick, then run lppick manually, I do not get the
"lppick: SIGSEGV" message when I shutdown d3....also strace doesn't
seem to catch any exception when I shutdown d3.

Thanks,
Richard Ottinger
Eastex Crude Company



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.