alphamikevictor's questions

I have a job launched in a screen session which is expected to run for several hours. From time to time I'm requested to check if job is still running and guess at wich % of work is.

Guess if it is working or not is as simple as perform a ps -fu $LOGNAMEto check if the process is still alive, but in order to guess the % I need to check the output of the program (it outputs some information which can be used with grep -n to see which line of file it is currently processing).

I can attach the session (screen -R jobLoadItems) and take a look to it, but I would like to do it without attaching to session again. I already checked to perform inside the screen session Ctrla-H to activate screenlog but it's so verbooooooooose it will take all disk space available.

So there is a way to just print last lines of the screen session without attaching to it? (something like screen -S jobLoadItem -Q display last 50 lines)

I'm using an Apache 2.2 in order to access a Microsoft Team Foundation Server 2015 configured to use NTML.

My configuration for this purpose is the following:

ProxyPreserveHost On
ProxyPass /tfs/ http://tfs2015.mdlp.es:8080/tfs/
ProxyPassReverse /tfs/ http://tfs2015.mdlp.es/tfs/

Apparently this configuration works pretty fine when there is only one user. When a seccond user connects it appears as the user previously logged.

I guess this is happening due to the connection pool apache maintains against the backend server, and it is like TFS once the user on this keepalive connection is authenticated relies on the first requests to be aware about the user. As far as apache will forward all requests to the already created pool, this will mix user sessions in the same keep alive connection.

At this point I've tried to use the disablereuse=On directive on ProxyPass in order to avoid the use of connection pooling, but this way the NTLM authentication is not working.

Just wondering if anyone was able to solve this problem, which perhaps is not related 100% to Team Foundation but to IIS.

EDIT:

As far as I have an apache 2.0 installed on the same Reverse Proxies I've tried to configure them the same way, and it works properly. So there is a way to limit the proxypass features on apache 2.2 to behave like apache 2.0?

I have a strange issue with 2 rra files, each time I try to update them rrdtool update never finishes.

This is the definition of one of RRA files:

/usr/bin/rrdtool create \
/var/www/cacti/rra/siebel_-_oam_01_errortests_633.rrd \
--step 120  \
DS:miliseconds:GAUGE:240:0:U \
DS:oktests:GAUGE:240:0:U \
DS:errortests:GAUGE:240:0:U \
RRA:AVERAGE:0.5:1:500 \
RRA:AVERAGE:0.5:1:600 \
RRA:AVERAGE:0.5:6:700 \
RRA:AVERAGE:0.5:24:775 \
RRA:AVERAGE:0.5:1:105120 \
RRA:AVERAGE:0.5:288:797 \
RRA:MIN:0.5:1:500 \
RRA:MIN:0.5:1:600 \
RRA:MIN:0.5:6:700 \
RRA:MIN:0.5:24:775 \
RRA:MIN:0.5:1:105120 \
RRA:MIN:0.5:288:797 \
RRA:MAX:0.5:1:500 \
RRA:MAX:0.5:1:600 \
RRA:MAX:0.5:6:700 \
RRA:MAX:0.5:24:775 \
RRA:MAX:0.5:1:105120 \
RRA:MAX:0.5:288:797 \
RRA:LAST:0.5:1:500 \
RRA:LAST:0.5:1:600 \
RRA:LAST:0.5:6:700 \
RRA:LAST:0.5:24:775 \
RRA:LAST:0.5:1:105120 \
RRA:LAST:0.5:288:797

This is one sample command I use to update:

rrdtool update /var/www/cacti/rra/siebel_-_oam_01_errortests_633.rrd -t miliseconds:oktests:errortests 1433402040296:17:20:0

Due to an error some of the Published applications in our farm (Citrix 4.5) were deleted. As far as we have the datastore in Oracle probably restoring our last backup before the accidental deletion will solve the problem.

But before performin this action (recover the database used for farm datastore) I've take a look to the database and I realized there is a table called DELETETRACKER which seems to hold the already deleted applications in Citrix.

On this table there is a field called smallentry which seems to hold the application configuration. I wonder if there is a way to see this field on a human readable way so we can recover the information of those deleted applications and publish them again manually.