Yes I think the way the dependencies are set in the packages updating one
will potentially update the rest, so best to do the update off hours, and
if possible (if it's a VM for example) take a snapshot or back up of your
config and database first.

On Fri, Mar 25, 2016 at 12:14 PM Konstantin Raskoshnyi <[email protected]>
wrote:

> Yep. I double checked the version, and it's 2.3.
> Is it necessary to update the whole packages with yum?
> It's the main deployment server. Don't want to get any troubles :).
> Thanks!
>
>
> On Friday, March 25, 2016, Matt Moldvan <[email protected]> wrote:
>
>> Cool, I was thinking you were already at 2.4 from your earlier reply.
>> Either way good luck and let us know if it solves your issue in case anyone
>> has the same question in the future.
>>
>> > The spacewalk version is 2.4, Oct 7th, 2015 Thanks!
>>
>> On Thu, Mar 24, 2016 at 11:15 PM Konstantin Raskoshnyi <
>> [email protected]> wrote:
>>
>>> Hi Matt!
>>>
>>> I tried to tune tomcat, but looks like here's my problem
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1214437
>>>
>>> Going to upgrade to version 2.4..
>>>
>>> Thanks!
>>>
>>> On Thu, Mar 24, 2016 at 8:06 PM, Matt Moldvan <[email protected]> wrote:
>>>
>>>> What are your tomcat settings like?  We have maxThreads set to 2048 for
>>>> the 8009 and 8080 connectors in /etc/tomcat6/server.xml:
>>>>
>>>>     <Connector port="8080" protocol="HTTP/1.1"
>>>> connectionTimeout="20000" redirectPort="8443" maxThreads="2048"
>>>> maxKeepAliveRequests="1024" URIEncoding="UTF-8" address="127.0.0.1"/>
>>>>     <Connector port="8009" protocol="AJP/1.3" redirectPort="8443"
>>>> URIEncoding="UTF-8" address="127.0.0.1" maxThreads="2048"
>>>> maxConnections="2048" connectionTimeout="600" keepAliveTimeout="600"/>
>>>>
>>>> Also, /etc/tomcat6/tomcat6.conf has some settings for JAVA_OPTS that
>>>> are interesting for tuning purposes:
>>>>
>>>> JAVA_OPTS="-XX:NewRatio=4 -XX:PermSize=1024m -XX:MaxPermSize=2048m
>>>> -XX:NewSize=2048m -XX:MaxNewSize=2048m -Xms8g -Xmx8g -XX:+UseParNewGC
>>>> -XX:+UseConcMarkSweepGC -Dsun.rmi.dgc.client.gcInterval=3600000
>>>> -Dsun.rmi.dgc.server.gcInterval=3600000"
>>>>
>>>> Listing 500 systems on our master took ~10.22 seconds on an 8 vCPU/32GB
>>>> RAM VMware VM, with an external Postgres database VM that has 8 vCPU/16GB
>>>> RAM, so yours could be much quicker with some additional tuning, I would
>>>> think.
>>>>
>>>>
>>>> On Thu, Mar 24, 2016 at 10:01 PM Konstantin Raskoshnyi <
>>>> [email protected]> wrote:
>>>>
>>>>> The spacewalk version is 2.4, Oct 7th, 2015
>>>>>
>>>>> Thanks!
>>>>>
>>>>> On Thu, Mar 24, 2016 at 6:21 PM, William H. ten Bensel <
>>>>> [email protected]> wrote:
>>>>>
>>>>>> What version of spacewalk are you running?
>>>>>>
>>>>>> Bill
>>>>>>
>>>>>> On Mar 24, 2016, at 20:15, Konstantin Raskoshnyi <[email protected]>
>>>>>> wrote:
>>>>>>
>>>>>> This email originated from outside of the company. Please use
>>>>>> discretion if opening attachments or clicking on links.
>>>>>> ------------------------------
>>>>>>
>>>>>> Hi Community!
>>>>>> We have a spacewalk server on SCLinux 7.1, Java 1.7 and postgres
>>>>>> When I open Systems menu (list servers) and list whole 250 nodes - it
>>>>>> takes about 90 seconds.
>>>>>> The java process shows 400%.
>>>>>> The server has 64Gb of Ram and 24 cores.
>>>>>> Thought the problem in postgres, actually i got the query from the
>>>>>> log file, the query runs about 8seconds.
>>>>>> All other time Java doing something...
>>>>>> Any solutions?
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> **
>>>>>>
>>>>>>
>>>>>>
>>>>>> This email and any attachments may contain information that is
>>>>>> confidential and/or privileged for the sole use of the intended 
>>>>>> recipient.
>>>>>> Any use, review, disclosure, copying, distribution or reliance by others,
>>>>>> and any forwarding of this email or its contents, without the express
>>>>>> permission of the sender is strictly prohibited by law. If you are not 
>>>>>> the
>>>>>> intended recipient, please contact the sender immediately, delete the
>>>>>> e-mail and destroy all copies.
>>>>>>
>>>>>> **
>>>>>>
>>>>>> _______________________________________________
>>>>>> Spacewalk-list mailing list
>>>>>> [email protected]
>>>>>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Spacewalk-list mailing list
>>>>> [email protected]
>>>>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>>>>
>>>>
>>>> _______________________________________________
>>>> Spacewalk-list mailing list
>>>> [email protected]
>>>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>>>>
>>>
>>> _______________________________________________
>>> Spacewalk-list mailing list
>>> [email protected]
>>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>>
>> _______________________________________________
> Spacewalk-list mailing list
> [email protected]
> https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list

Reply via email to