I'm running spacewalk 1.9 on 32-bit CentOS 5.9. I'm having two problems and 
would appreciate suggestions on troubleshooting them.

The first one is that my SLES channels are not syncing correctly, with an error 
message generated for each package: "int() argument must be a string or a 
number". I have an mrepo server which is using our credentials with Novell to 
pull down the packages and build a yum repository. I don't see any errors in 
that and I do see that new packages are appearing in the repository as they are 
found. Our spacewalk server points to those repositories on the mrepo server. 
The same mrepo server builds RHEL repositories and they sync with spacewalk 
with no errors. Here is the output from a repo sync:

# spacewalk-repo-sync --channel sles11-sp2-updates-x86_64 --type yum
Repo URL: http://mrepo.server/mrepo/sles11-x86_64/RPMS.sp2-updates/
Packages in repo: 4750
Packages already synced: 908
Packages to sync: 3766
1/3766 : php53-xsl-5.3.8-0.27.1-0.x86_64
int() argument must be a string or a number
2/3766 : gvfs-1.4.3-0.17.19.1-0.x86_64
int() argument must be a string or a number
3/3766 : glibc-info-2.11.3-17.45.45.1-0.x86_64
int() argument must be a string or a number
4/3766 : nautilus-2.28.4-1.16.16.4-0.x86_64
int() argument must be a string or a number
5/3766 : hwinfo-15.48-0.6.6.1-0.x86_64
int() argument must be a string or a number
6/3766 : libproxy0-config-kde4-0.3.1-2.6.3-0.x86_64
int() argument must be a string or a number


The second problem is that when we access our spacewalk server using firefox, 
safari, or chrome we get an error that pops up from time to time at seemingly 
random points which says "A server error has occurred". We click OK and carry 
on and it seems to work ok. I'm told users don't get the error when they are 
using IE.

I don't think I can find anything in the logs in the following directories at 
the same time although it's hard to be sure because I can't create it 
deliberately:
/var/log/tomcat5
/var/log/rhn
/var/log/httpd

I have seen this in catalina.out sometimes around the time it happens, but not 
always:
WARNING: Error sending end packet
java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:538)
at org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:127)
at org.apache.jk.core.MsgContext.action(MsgContext.java:302)
at org.apache.coyote.Response.action(Response.java:183)
at org.apache.coyote.Response.finish(Response.java:305)
at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:205)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:775)
at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:704)
at 
org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:897)
at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685)
at java.lang.Thread.run(Thread.java:679)

Is there somewhere else I should be looking?

Thanks,
Maria

_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list

Reply via email to