printQ.debug 1

[pb111]

Can anyone tell me what printQ.debug file does? It is in my TMP Dir and I think it is causing my print files to store in the personnel profile directory.

I have a RS6000 using AIX 4.x

Thank you in advance.

Paul

 

[aixqueen]

I do not recognize it as an AIX file. Do you have a third party like Easy Spool or
something on your machine?

As you know normal is usually /var/spool for files..........

even the AIX trace is not named printQ.debug....

I suppose someone could have set up an iptrace for the printers....

http://techsupport.services.ibm.com..._mode=9&documents=39175597789870&database=aix

 

[pb111]

Thank you for your reply, here is some more information about my problem.
Yes printQ.debug was written by a programmer we employeed many years ago.


##############Starting for root at root pts/7 Sep 06 07:18 (192.
130.80.141)
+ set -o vi
+ alias cls=clear
+ alias stat=enq -A -W
+ PS1=$PWD:>
+ + tty
+ cut -c6-
TTY=pts/7
+ echo pts/7
+ grep pts
+ 1> /dev/null 2>& 1
+ [ 0 -eq 0 ]
+ + who am i
+ grep root
+ cut -c42-
IPINIT=192.130.80.141)
+ + wc -c
+ echo 192.130.80.141)
IPCHAR1= 16
+ + expr 16 - 2
IPCHAR2=14
+ + cut -c1-14
+ echo 192.130.80.141)
IPADDR=192.130.80.141
+ PRINTER=complaser
+ [ root = ucr ]
+ echo complaser

##############Starting for root at root pts/0 Sep 06 07:41 (192.
130.80.141)
+ set -o vi
+ alias cls=clear
+ alias stat=enq -A -W
+ PS1=$PWD:>
+ + tty
+ cut -c6-
TTY=pts/0
+ grep pts
+ echo pts/0
+ 1> /dev/null 2>& 1
+ [ 0 -eq 0 ]
+ + who am i
+ cut -c42-
+ grep root
IPINIT=192.130.80.141)
+ + wc -c
+ echo 192.130.80.141)
IPCHAR1= 16
+ + expr 16 - 2
IPCHAR2=14
+ + cut -c1-14
+ echo 192.130.80.141)
IPADDR=192.130.80.141
+ PRINTER=complaser
+ [ root = ucr ]
+ echo complaser

##############Starting for root at root pts/2 Sep 06 07:46 (192.
130.80.141)
+ set -o vi
+ alias cls=clear
+ alias stat=enq -A -W
+ PS1=$PWD:>
+ + tty
+ cut -c6-
TTY=pts/2
+ grep pts
+ echo pts/2
+ 1> /dev/null 2>& 1
+ [ 0 -eq 0 ]
+ + who am i
+ grep root
+ cut -c42-
IPINIT=192.130.80.141)
+ + echo 192.130.80.141)
+ wc -c
IPCHAR1= 16
+ + expr 16 - 2
IPCHAR2=14
+ + cut -c1-14
+ echo 192.130.80.141)
IPADDR=192.130.80.141
+ PRINTER=complaser
+ [ root = ucr ]
+ echo complaser

##############Starting for root at root pts/3 Sep 06 07:48 (192.
130.80.141)
+ set -o vi
+ alias cls=clear
+ alias stat=enq -A -W
+ PS1=$PWD:>
+ + cut -c6-
+ tty
TTY=pts/3
+ echo pts/3
+ grep pts
+ 1> /dev/null 2>& 1
+ [ 0 -eq 0 ]
+ + who am i
+ grep root
+ cut -c42-
IPINIT=192.130.80.141)
+ + echo 192.130.80.141)
+ wc -c
IPCHAR1= 16
+ + expr 16 - 2
IPCHAR2=14
+ + echo 192.130.80.141)
+ cut -c1-14
IPADDR=192.130.80.141
+ PRINTER=complaser
+ [ root = ucr ]
+ echo complaser

##############Starting for root at root pts/0 Sep 06 09:52 (192.
130.80.141)
+ set -o vi
+ alias cls=clear
+ alias stat=enq -A -W
+ PS1=$PWD:>
+ + cut -c6-
+ tty
TTY=pts/0
+ echo pts/0
+ grep pts
+ 1> /dev/null 2>& 1
+ [ 0 -eq 0 ]
+ + who am i
+ cut -c42-
+ grep root
IPINIT=192.130.80.141)
+ + echo 192.130.80.141)
+ wc -c
IPCHAR1= 16
+ + expr 16 - 2
IPCHAR2=14
+ + echo 192.130.80.141)
+ cut -c1-14
IPADDR=192.130.80.141
+ PRINTER=complaser
+ [ root = ucr ]
+ echo complaser

##############Starting for root at root pts/0 Sep 06 11:33 (192.
130.80.141)
+ set -o vi
+ alias cls=clear
+ alias stat=enq -A -W
+ PS1=$PWD:>
+ + cut -c6-
+ tty
TTY=pts/0
+ echo pts/0
+ grep pts
+ 1> /dev/null 2>& 1
+ [ 0 -eq 0 ]
+ + who am i
+ cut -c42-
+ grep root
IPINIT=192.130.80.141)
+ + wc -c
+ echo 192.130.80.141)
IPCHAR1= 16
+ + expr 16 - 2
IPCHAR2=14
+ + cut -c1-14
+ echo 192.130.80.141)
IPADDR=192.130.80.141
+ PRINTER=complaser
+ [ root = ucr ]
+ echo complaser


The error reads:
The file access permissions do not allow the specified action.
/usr/local/bin/printQ[2]: /tmp/printQ.debug: 0403-005 Cannot create the specifie
d file.
The file access permissions do not allow the specified action.
/usr/local/bin/printQ[3]: /tmp/printQ.debug: 0403-005 Cannot create the specifie
d file.
The file access permissions do not allow the specified action.
/usr/local/bin/printQ[4]: /tmp/printQ.debug: 0403-005 Cannot create the specifie
d file.


It seems when we print the file goes to our individual profiles. in the Home Dir.

I signed on as Root and renamed the printQ.debug to printQ.bak in the /TMP directory. I was able to print but no one else was.

I did a grep and found another file called printQ.debug on the RS6000 in the

./usr/local/bin/printQ.debug Directory looks like this

/usr/local/bin:> cat printQ.debug
#!/bin/ksh -x
#
# Name: printQ
#
#Script to determine which printq a terminal should use
#Created by Joe Murphy, IBM, 6/28/94. Modeled on /usr/bin/ncic.original
# Updated on 9/11/96 fby Joe Murphy for EWIND TWSP
#
# $TTY is set by /etc/profile and exported.
#
# PrintQ is determined by which Termin or IP address they comm from
#
echo $TTY | grep pts >/dev/null 2>&1 # TTY is gotten from /etc/kshrc
#echo $1 | grep pts >/dev/null 2>&1 # TTY is gotten from /etc/kshrc
if [ $? -eq 0 ]
then
#This is a TCP/IP device - pts/0 is part of the device
#Determine hostname or IP Address logging in from
IPINIT=`who am i|grep $LOGNAME| cut -c42-`
IPCHAR1=`echo $IPINIT | wc -c`
IPCHAR2=`expr $IPCHAR1 - 2`
IPADDR=`echo $IPINIT | cut -c1-$IPCHAR2`
#IPADDR=$IPADDR
#else This is a regular tty device
fi
#echo "TESTING ONLY - your terminal is $TTY"
#echo "NCIC is not ready yet...."
#echo "Press the return key to return to the menu"
#read junk
#exit 0

case $IPADDR in
192.130.80.111|192.130.80.112) PRINTER=ptlt ;;
192.130.80.113|192.130.80.114|192.130.80.115) PRINTER=comm ;;
192.130.80.116|192.130.80.117|192.130.80.118|192.130.80.119) PRINTER=comm ;;
192.130.80.120|192.130.80.121|192.130.80.122|192.130.80.123) PRINTER=comm ;;
192.130.80.129|192.130.80.128|192.130.80.127|192.130.80.124|192.130.80.125|1
92.130.80.126) PRINTER=record2 ;;
192.130.80.133|192.130.80.132|192.130.80.130|192.130.80.131) PRINTER=traffic
;;
192.130.80.134|192.130.80.135|192.130.80.136|192.130.80.137|192.130.80.138)
PRINTER=admin ;;
192.130.80.139|192.130.80.140|192.130.80.141) PRINTER=complaser ;;
192.130.80.145|192.130.80.147|192.130.80.146) PRINTER=juvenile2 ;;
192.130.80.148|192.130.80.149|192.130.80.150|192.130.80.151) PRINTER=db ;;
192.130.80.152|192.130.80.153|192.130.80.154|192.130.80.155) PRINTER=db ;;
192.130.80.156|192.130.80.164) PRINTER=db ;;
192.130.80.160|192.130.80.157|192.130.80.158|192.130.80.159) PRINTER=nsulas
er ;;
192.130.80.161|192.130.80.162) PRINTER=booking ;;
ewing) PRINTER=complaser ;;
*) PRINTER=comm ;;
esac
if [ $LOGNAME = ucr ]
then PRINTER=ucr2
fi

echo $PRINTER


One other file in this Directory is
printQ.new
/usr/local/bin:> cat printQ.new
#!/bin/ksh
/usr/local/bin/printQ.debu 2>>/tmp/printQ.debug



I am so sorry, if I over dosed you with information. It's just that I am getting heat for 40 other workstations that are not printing.

THANK YOU VERY MUCH
Paul

 

[aixqueen]

1)It looks like a program that was set up a long time ago to have a user log in and
determine where they are coming from ( who they are and where they are) and then only allow them to print to a specific printer set up by their location............ It would have been easier to have an LPDEST statement in their profile but oh well......I assume that your users move around alot? Maybe that is why they did it that way.


2)The question is what do you want to do?

3)What are the permissions on /usr/local/bin? and who owns it and what is their group?
What are the permissions on /tmp and who owns it?
drwxrwsrwt 16 bin bin 4608 Nov 27 14:32 /tmp

-------------------------------
4)
0403-005

Cannot create the specified file
Possible Causes
From the command line, you issued the following command:

cat Filename > Printdevice

The printer device was either not attached, was busy, was down, or was on
the network.

You attempted to create a file in a directory for which you do not have write
or execute permissions.

You attempted to write to a file system that is mounted as read-only.

Procedures for Recovery

Ensure that the printer device is attached to the system.

Run the lpstat command to check if the printer is busy, or if the print queue
is down. If the printer is busy, wait until the currently queued job is
complete, and rerun the command.

If the print queue is down, run the su command to become the root user,
and then run the qadm command to restart the queue:

qadm -U Queuename

Run the su command and become the root user.
Add read/write permission to the directory and to the parent directories.

Unmount the file system with the unmount <filesystem> command.

Remount the file system with read/write access:

mount -o rw Filesystem Directory

======================
5) Check the permissions for normal printing...

File permissions, owners and groups for printing....

Check and make sure they are
similar...not sure what the /usr/local/bin/directory was..........maybe 755? 777?

At minimum, the following should be checked. This is especially true if only the root user (superuser) can
print.

-r-sr-s--- 1 root printq 58989 Oct 26 1994 /usr/sbin/qdaemon
-r-sr-s--- 1 root printq 50099 Oct 26 1994 /usr/sbin/lpd
-r-sr-sr-x 1 root printq 59262 Oct 26 1994 /bin/enq
-r-xr-xr-x 1 bin bin 31493 Oct 26 1994 /bin/qprt
-r-xr-xr-x 1 bin bin 30397 Oct 26 1994 /bin/lp
-r-xr-xr-x 1 bin bin 31421 Oct 26 1994 /bin/lpr
-r-xr-xr-x 1 bin bin 30909 Oct 26 1994 /bin/lpstat
-r-xr-sr-x 1 bin printq 54633 Oct 13 1994 /usr/lib/lpd/piobe
-r-sr-x--- 1 root printq 38205 Oct 26 1994 /usr/lib/lpd/digest
-r-sr-x--- 1 root printq 52088 Oct 26 1994 /usr/lib/lpd/qstatus
-r-sr-xr-x 1 root printq 49626 Aug 14 1995 /usr/lib/lpd/pio
/etc/pioout
crw-rw-rw- 1 root system 2, 2 Jul 09 08:56 /dev/null
-rw-rw-r-- 1 root printq 6198 Sep 27 10:55 /etc/qconfig
-rw-rw---- 1 root printq 26876 Sep 27 10:55 /etc/qconfig.bin
drwxr-xr-x 33 bin bin 2048 Sep 17 00:39 /
drwxr-xr-x 12 bin bin 512 Jul 10 14:45 /var
drwxrwxr-x 12 bin bin 512 Sep 13 18:53 /var/spool
drwxrwxr-x 5 bin printq 14336 Sep 14 11:51 /var/spool/lpd
drwxrwxr-x 2 root printq 42496 Sep 15 17:19 /var/spool/lpd/qdir
drwxrwxr-x 2 root printq 2048 Sep 15 17:18 /var/spool/lpd/stat
drwxrwxr-x 2 bin printq 6656 Sep 15 15:23 /var/spool/qdaemon
drwxr-xr-x 21 bin bin 512 Jan 17 1995 /usr
drwxr-xr-x 3 bin bin 11776 Sep 16 23:31 /usr/bin
drwxr-xr-x 4 bin bin 9216 Sep 16 23:32 /usr/sbin
drwxrwxr-x 15 root system 8192 Sep 27 10:55 /etc
drwxrwsrwt 16 bin bin 4608 Nov 27 14:32 /tmp

To check directories, enter:

ls -ld <path/directory>

For example, ls -ld / would return information for root directory, and ls -ld /etc would return information.

6) What changed....what happened that it stopped working...new printer added, ? Someone changed permissions on a directory? Something must have changed for it to stop working all of a sudden? Any clues?

It is a big problem....and not easily solved here.........The above may help you.....
but if not.....several things......If it just stopped working and you can find out what changed, change it back? If not when is the last mksysb from when it was working?
Can you go back? You could install new patches for bos.rte.printers and printers.rte and it may fix a permission problem........but guess if it will totally fix things.........
Did someone mess with permissions on other things as well?

Good Luck........

 

[aixqueen]

one last thought...
make sure nothing is full filesystem wise

df

and see that you have space...sometimes it cannot write if you are out of space.

 

[pb111]

Nothing seems to be working.
I've enclosed a copy of the /tmp directory

/tmp:> ls -lpatr
total 104
drwx------ 2 root system 512 Jun 07 13:26 lost+found/
drwxr-xr-x 3 root system 512 Jun 13 13:42 vgdata/
drwxrwxr-x 3 root system 512 Jun 14 03:01 bos/
-rw------- 1 root system 0 Sep 06 07:36 .strload.mutex
-rw-rw-rw- 1 root system 13 Sep 06 07:37 rc.net.out
-rw-rw-rw- 1 root system 0 Sep 06 07:38 ncicmon.out
-rw-rw-rw- 1 root system 0 Sep 06 07:38 startprinter.out
-rw-rw-rw- 1 root system 894 Sep 06 07:38 ncicmon.local.out
srwxrwxrwx 1 root system 0 Sep 06 07:39 .PMDV1
-rw-rw-rw- 1 root system 16 Sep 06 07:39 last_uuid
drwxr-xr-x 19 bin bin 2048 Sep 06 13:07 ../
-rw-r--r-- 1 root system 699 Sep 07 03:01 cleanup.out
-rw-r--r-- 1 root system 40 Sep 07 10:03 users.pid
-rw-r--r-- 1 root system 4515 Sep 07 10:36 printQ.bak
-rw-r--r-- 1 mb22 staff 498 Sep 07 10:36 printQ.debug
drwxrwxrwt 5 bin bin 1536 Sep 07 10:36 ./
/tmp:>
mb22 is a user - she popped on when I renamed printQ.debug, she is the only one that can print.

Any other ideas ?
Tks paul

 

[vickersdc]

I've only just scanned through this quickly, but could the file permissions on printQ.debug be incorrect - should it have SUID or SGID set?

Just a thought.

Cheers.
Dave V.

 

[pb111]

Great news.
The problem is solved. Thanks to the support I got here !

I used the chmod command and increased the permissions to the printQ files and it seems to work.


Thanks again

Paul

 

[aixqueen]

Do you have an old mksysb of the printQ.debug and other files that are part of this when it was working?

You could check its original permissions....

You are probably right DAVE........ rw r r seems wrong... at least should be 755 ...
for a script.......same with file in /usr/local/bin........but we are guessing......if it needs to be run as root....the script looks like it uses the users profile..... who you are to determine what printer...so it may not need suid or sgid....hard to tell.
If you had it on tape, it would be easier to find what it was and change it back.

AS I SAID before...what changed? What happened all of a sudden that it stopped working....? System crash...programmers playing? IP address change? That is the clue you need to solve it.......

I would change the permission on printQ.debug (where ever it is (both directories)
to at least 755..but unless you have a document with it on it...we are all guessing.

 

[pb111]

The answer to my problem was

chmod 777 /tmp/printQ.debug

&quot;You all were a tremendous help to me&quot;, and I thank you very very much..

Paul