We're here to help!

If You Are Getting "the Page Isn't Redirecting Properly" Messages in Dbvisit Standby GUI

Follow

Read our docs When Dbvisit Standby is used and Dbvserver has been running for some time, and you suddenly start getting redirect messages in the browser, the most likely cause of this is that required temporary files used by Dbvserverd in the /tmp filesystem was removed.


Problem Details

Problem Statement

dbvserver web starts to behave odd and we get error.

Applicable Error Code

The Page Isn't Redirecting Properly

Affected Versions

Version 7.0 

Affected Platforms

Noticed in Unix environments

 

Description

Note: if you are using Dbvisit Standby version 7, please make sure you are running version 7.0.10 and above as version 7.0.10 implemented changes that will reduce the risk of getting this error.

When running Dbvisit Standby on Linux, you might have the default tmpwatch cron schedule running under:

/etc/cron.hourly
/etc/cron.daily
/etc/cron.weekly

Dbvserver is creating temporary files as part of normal execution in /tmp filesystem. If you have tmpwatch running, it might clean up these files which is still used by dbvserver processes. This can cause the issue where you have redirect messages such as The page isn't redirecting properly.


Solution/Example
oracle@dbvlin501[/tmp]:**ls -al**total 32
drwxrwxrwt   4 root root 4096 Aug 11 19:36 .
drwxr-xr-x  27 root root 4096 Aug  9 11:12 ..
drwxrwxrwt   2 root root 4096 Aug  9 11:12 .font-unix 
drwxrwxrwt   2 root root 4096 Aug  9 11:12 .ICE-unix
oracle@dbvlin501[/tmp]: /usr/local/dbvisit/dbvserverd start
oracle@dbvlin501[/tmp]: ls -al
total 40
drwxrwxrwt   5 root   root     4096 Aug 11 19:36 .
drwxr-xr-x  27 root   root     4096 Aug  9 11:12 ..
drwxr-xr-x   4 oracle oinstall 4096 Aug 11 19:36**dbvtmp-8663**drwxrwxrwt   2 root   root     4096 Aug  9 11:12 .font-unix
drwxrwxrwt   2 root   root     4096 Aug  9 11:12 .ICE-unix
oracle@dbvlin501[/tmp]:

If you login to the GUI it should work fine, but if I now go and remove the /tmp/dbvtmp-8663 directory and then try and use the GUI I start getting The page isn't redirecting properly messages. This will require the restart of dbvserverd to resolve.

In summary, if you can please review your cron schedules for tmpwatch and update it to exclude the dbvtmp-* directory from being purged if using version 6 and that you exclude dbvtmp-* and par-* from being excluded in version 7.

To exclude this directory from the tmpwatch schedule you can update the exclusion list. For example: I add the following exclusion:

-X '/tmp/dbvtmp-*' -X '/tmp/p2xtmp-*'  -X '/tmp/par-*' -X '/tmp/pdk-*'  

in /etc/cron.daily/tmpwatch to exclude these temporary cache directories.

Below is an example /etc/cron.daily/tmpwatch script from an Oracle Linux 5 environment.

flags=-umc
/usr/sbin/tmpwatch "$flags" -x /tmp/.X11-unix -x /tmp/.XIM-unix -x /tmp/.font-unix -x /tmp/.ICE-unix -x /tmp/.Test-unix**-X '/tmp/p2xtmp-\*'****-X '/tmp/dbvtmp-\*'****-X '/tmp/par-\*' -X '/tmp/pdk-\*'**240 /tmp
/usr/sbin/tmpwatch "$flags" 720 /var/tmp
for d in /var/{cache/man,catman}/{cat?,X11R6/cat?,local/cat?}; do
    if [ -d "$d" ]; then
    /usr/sbin/tmpwatch "$flags" -f 720 $d
    fi
done

Note: if using a pattern, use (uppercase) -X if using absolute path then use -x (lowercase x). For more detail see man tmpwatch

Important

If you are getting this issue, follow these steps:

  1. Update the tmpwatch job or any other jobs you might have that might be cleaning up the /tmp location to exclude these p2xtmp-, dbvtmp- and par- directories.

    Example updated tmpwatch on OEL5 environment:

    flags=-umc
    /usr/sbin/tmpwatch "$flags" -x /tmp/.X11-unix -x /tmp/.XIM-unix -x /tmp/.font-unix -x /tmp/.ICE-unix -x /tmp/.Test-unix**-X '/tmp/p2xtmp-\*'****-X '/tmp/dbvtmp-\*'****-X '/tmp/par-\*' -X '/tmp/pdk-\*'**240 /tmp
    /usr/sbin/tmpwatch "$flags" 720 /var/tmp
    for d in /var/{cache/man,catman}/{cat?,X11R6/cat?,local/cat?}; do
        if [ -d "$d" ]; then
        /usr/sbin/tmpwatch "$flags" -f 720 $d
        fi
    done

    Note: if using a pattern, use (uppercase) -X if using absolute path then use -x (lowercase x). For more detail see man tmpwatch

  2. Stop Dbvisit Standby components (Dbvserver if using version 6 and Dbvserver + Dbvnet if using version 7)

    Example stop of components (below include dbvnet - version 7 only):

    cd /usr/dbvisit/dbvnet
    ./dbvnetd stop
    cd /usr/dbvisit/dbvserver
    ./dbvserverd stop
  3. Remove all directories in /tmp starting with: p2xtmp-, dbvtmp- , par- and pdk-

    cd /tmp
    rm -Rf p2xtmp-*
    rm -Rf dbvtmp-*
    rm -Rf par-*
    rm -Rf pdk-*
  4. Restart the the Dbvisit Standby components. Example (including dbvnet - version 7 only):
    cd /usr/dbvisit/dbvnet
    ./dbvnetd start
    cd /usr/dbvisit/dbvserver
    ./dbvserverd start
  5. Now login to the Web Based front-end.

Note: added 1 April 2014

Anton Els August 12, 2013 12:59

Have more questions? Submit a request

Comments

  • Avatar
    Arjen Visser
    Thanks Anton. I beat my head a bit over this one. I had the beta of 7 installed, removed the binaries, and installed the released version. The GUI just wouldn't come up. Finding this while I was entering a support request saved me a day. I also found dbvisit files in a /tmp/par-* directory. I went ahead and removed them but not sure I needed to as the names seemed more like they came during the install. Anyway, thanks for posting your solution. Mark Weeden