After the last update of SMT, the clients are unable to get jobs from
the server.
The process smt-agent is blocked (the message is “Error: Cannot open
Lock. Process still running?”), and the client receive the 404 error
from smt server (object not found).
In /var/log/apache2/error_log i see the error
Use of uninitialized value in concatenation (.) or string at
/usr/lib/perl5/vendor_perl/5.10.0/SMT/JobQueue.pm line 276
Same problem here as well!
The agents ask for their referring job - everything is fine with the
database as far as I can see - but the SMT server returns a HTTP-error
404 - Page not found - including the mentioned log entry regarding the
variable. The major problem is that the agents to not finish their
connection and the SMT server gets filled up with network connections in
a FIN_WAIT-state.
Problem: patch:slesmtsp0-res-signingkeys-5162.noarch conflicts with
smt.x86_64 < 1.1.22-0.2.1 provided by smt-1.1.21-0.2.1.x86_64
Solution 1: do not keep smt-1.1.21-0.2.1.x86_64 installed
Solution 2: do not install
patch:slesmtsp0-res-signingkeys-5162.noarch
Choose from above solutions by number or cancel [1/2/c] (c): c
…
_20-Product: SMT 1.1.22-0.2.1
_21-Defect: SMT agent queries to the server fail with a 404 response.
in the apache2 error log, seeing “Use of uninitialized value in
concatenation (.) or string at
/var/lib/perl5/vendor_perl/5.10.0/SMT/Jobqueue.pm line 276.”
Consequently, the smt agents fail to disconnect, eventually filling
Apache’s connections to capacity.
_22-Other_Product: n/a
_23-Steps: Have SMT running latest set of updates.
_24-Other_Scenarios: Didn’t try others
_25-Environment_Description: SLES-11-SP1 server; SLES-10-SP3,
SLES-11-SP1 and SLED-11-SP1 agents.
_26-Reported: Production
_27-Testing_Environment: Didn’t try that
_28-Fix: n/a
_22-Additional: /var/lib/perl5/vendor_perl/5.10.0/SMT/Jobqueue.pm line
276 reads:
Hi Andreas and all
ollenburg;2148888 Wrote:[color=blue]
thanks for the update. Really looking forward for the solution. I guess
there is no working workaround at the moment?
[/color]
Workaround would be to downgrade smt to 1.1.21.
However that is not needed any more, since the problem is now fixed and
the patch is expected to be included in a on of the next maintenance
updates to the smt and smt-client packages.
Both the smt (and smt-support) packages on the SMT server as well as
the smt-client on the “managed” clients must be updated.
For those in desparate need of a resolution, we have created a
so-called mass PTF, which is a fully supported version of the packages
in question.
Please be sure to take the smt-client
(smt-client-0.0.14-0.3.1.3604.0.PTF.723901) from the latter block if you
are running SLE11SP1.
The smt-client-0.0.13-0.1.1.3573.1.PTF.723901 package in the SMT
directory is built only to comply with versioning policies.
I await said maintenance update with both bated breath and overflowing
mailboxes. Any ETA?
[/color]
Why are you awaiting the maintenance update when a PTF is available ?
A Problem Temporary Fix has only undergone limited testing (no QA like
maintenance updates), but is fully supported until the patch(es) it
contains is/are included in a maintenance update.
//Andreas
great news. Thanks. I installed the server and client on the SMT server
and it works.
BUT then I installed the SMT-client on a managed server (sles11sp1
32bit) and when running “smt-agent” I got this:
“Can’t locate XML/XPath.pm in @INC (@INC contains:
/usr/lib/perl5/5.10.0/i586-linux-thread-multi /usr/lib/perl5/5.10.0
/usr/lib/perl5/site_perl/5.10.0/i586-linux-thread-multi
/usr/lib/perl5/site_perl/5.10.0
/usr/lib/perl5/vendor_perl/5.10.0/i586-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.10.0 /usr/lib/perl5/vendor_perl .) at
/usr/lib/perl5/vendor_perl/5.10.0/SMT/Agent/RestXML.pm line 14.
BEGIN failed–compilation aborted at
/usr/lib/perl5/vendor_perl/5.10.0/SMT/Agent/RestXML.pm line 14.
Compilation failed in require at /usr/sbin/smt-agent line 7.
BEGIN failed–compilation aborted at /usr/sbin/smt-agent line 7.”
Uninstalling and installing the prior version there is no error. Any
ideas?
Hi,
Got the same error above:
Can’t locate XML/XPath.pm in @INC (@INC contains:
/usr/lib/perl5/5.10.0/x86_64-linux-thread-multi /usr/lib/perl5/5.10.0
/usr/lib/perl5/site_perl/5.10.0/x86_64-linux-thread-multi
/usr/lib/perl5/site_perl/5.10.0
/usr/lib/perl5/vendor_perl/5.10.0/x86_64-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.10.0 /usr/lib/perl5/vendor_perl .) at
/usr/lib/perl5/vendor_perl/5.10.0/SMT/Agent/RestXML.pm line 14.
BEGIN failed–compilation aborted at
/usr/lib/perl5/vendor_perl/5.10.0/SMT/Agent/RestXML.pm line 14.
Compilation failed in require at /usr/sbin/smt-agent line 7.
BEGIN failed–compilation aborted at /usr/sbin/smt-agent line 7.
Installed perl-XML-XPath
zypper in perl-XML-XPath
Got a new error when running smt-agent:
Error: Unable to request next job : Can’t connect to puppy.it.hb.se:443
(certificate verify failed)
You can disable hostname check by setting environment variable
PERL_LWP_SSL_VERIFY_HOSTNAME=0
LWP::Protocol::https::Socket: SSL connect attempt failed with unknown
errorerror:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate
verify failed at /usr/lib/perl5/vendor_perl/5.10.0/LWP/Protocol/http.pm
line 57.
When installing perl-XML-XPath-1.13-74.15 even the latest SMT-client ist
working. Did I miss any prereqs?[/color]
I have no idea why that one is not pulled in automatically.
But it should be installed to resolve the problems reported here.
It has not been observed in any of our labs and a number of customers
have reported nothing but success with the PTF.
//Andreas
When installing perl-XML-XPath-1.13-74.15 even the latest SMT-client ist
working. Did I miss any prereqs?[/color]
This is/was caused by the rare situation, where a patch introduces a
new dependency/pre-req. In this case something unfortunately went wrong
in the patch creation/build process, so the dependency on perl-XML-XPath
did not make it into the PTF
In the meantime, the updated SMT client (including the perl-XML-XPath
dependency) has been released publicly :
