after deployment the code changes are not reflecting in one node out of two nodes in cluster

to fix this you need to restart Node agent  then after try to sync Node even if still changes are not reflecting then copy installed application from installedApps from successfully installed node to unsuccessfully deployed node.

ensure to sync and restart dmgr ,node and jvm and check code changes are reflecting


if above does not work then check cus and blas available in cell level  in  unsuccessful node  are as same as working application code in fine and  working node.and then restart dmgr , nodeagent, JVM.

unstash the file and get password

#!/usr/bin/perl
use strict;
die "Usage: $0 <stash file>n" if $#ARGV != 0;
my $file=$ARGV[0];
open(F,$file) || die "Can't open $file: $!";
my $stash;
read F,$stash,1024;
my @unstash=map { $_^0xf5 } unpack("C*",$stash);
foreach my $c (@unstash) {
 last if $c eq 0;
 printf "%c",$c;
}
printf " ";



Unstashing steps:

Step 1: copy the above script into a perl script file (ex: unstash.pl  or py)

Step 2: run the file as ./unstash.pl filename.sth (ex: ./unstash.pl  filea.sth)

you will get the password after unstashing

Disabling the Directory Browsing in WebServer

In most of the Web servers Directory browsing is enabled by default.

to secure the code from Directory Browsing we need to disable the Directory Browsing using the below steps.

Before directory Browsing Disabled

Alias "/test/" "/testMachine/folder1/"

Directory "/testMachine/folder1/">
Options Indexes MultiViews
AllowOverride None
Order allow,deny
Allow from all
</Directory>

In Web Server httpd.conf find the above lines and replace Indexes with --Indexes.after making the changes code in httpd.conf file looks like below

After directory Browsing Disabled

Alias "/test/" "/testMachine/folder1/"

Directory "/testMachine/folder1/">
Options -Indexes MultiViews
AllowOverride None
Order allow,deny
Allow from all
</Directory>

Ensure you have restarted webservers to reflect the changes. before verifying clear browser cookies.

Note: in Few Apache based websevers even we can remove the word Indexes will also gives the same directory disabled behaviour.
to reflect the Directory browsing use correct webserver conf file and correct application accessible directory as mentioned above if you have mulplte applications configured in your webservers.

ClassNotFound Exception after installation of application | application url is giving 404 exception and giving classNotFound in logs

1.check the parent class first class loader policy is set.

2. make sure all required shared libraries is mapped to application.

3. check all the jar files are available at shared library location.

4. verify class path is set for the application is there is any.

disk space full alerts on /tmp which is 1GB size and there are no file available or all files available are taking less than 10MB on /tmp.

To free up the space on /tmp we have used below command to identify which process are taking space on /tmp. and restarted the process will free up the space on /tmp.

$lsof|grep -i wasadm|grep -i deleted

the above command lists all the open files and unmapped process using /tmp space and running with wasadm user.

after creating the datasource test connection is successful but when application is accessed that time it is giving error from newly creating server(WAS8.5) and it is not giving any error when accessible from the old server(WAS6.1).

issue is caused due to Microsoft SQL server went to read only mode, after Microsoft SQL server restart everything was working fine.

Application is not able to access from web seal servers and they were working fine from direct URL's.

issue is with web seal log file reached to 2GB so it stopped the responding .to resolve this we have renamed the log file and restarted the web seal server then application is able to access from the web seal servers as log rotation is made.

Webseal log Rotation

The websead msg log is not controlled from within the webseal conf file, but instead, via the routing file.

--------------------------------------------

The contents of the msg__webseald.log file come from webseal's STDERR, as controlled in the /opt/pdweb/etc/routing file

 FATAL:STDERR:-

ERROR:STDERR:-

WARNING:STDERR:-

The routing file can be modified to redirect these messages to a file, and the log file management can be configured at the same time.

 For example.

FATAL:UTF8FILE.10.10000:/var/pdweb/log/msg__webseald.log

ERROR:UTF8FILE.10.10000:/var/pdweb/log/msg__webseald.log

WARNING:UTF8FILE.10.10000:/var/pdweb/log/msg__webseald.log

Note:log file will be rotated after 10000 entries in any of file Fatal or error or warning log file .and max historical files are 10