RedHat Samba Mount Issue

[Max Drown (Infor)]

Cloverleaf 5.6, RedHat 5.0

I have a standard fileset-Local thread that receives a batch of files on a samba mount (cifs to a windows share) at 1am. It does not appear to see these files at all until the process is bounced. Once it is bounced, it sees and processes the files right away.

Example ‘ls -al’ before the process is bounced last two days:

-- Max Drown (Infor)

Topic

[Max Drown (Infor)]

Here is the mount command:

Code:

sudo mount -t cifs -o username=user,password=’pass’ //bhcqsload/cold /mnt/bhcqsload/cold

-- Max Drown (Infor)

[Russ Ross]

Max:

Since you observered the file isn’t seen until the process is cycled it might be worth looking at the time setting for the scan interval.

Russ Ross
RussRoss318@gmail.com

[Max Drown (Infor)]

They are set to defaults, 5/30.

-- Max Drown (Infor)

[Max Drown (Infor)]

Sending this to support:

Quote:

OS: RedHat 5.1

Cloverleaf: 5.6

01) On the Windows machine: create a share on a Windows server. Add a user called “hci” with full permissions.

02) On the Cloverleaf server: sudo mkdir -p /mnt/pc4422/qstesting

03) On the Cloverleaf server: sudo mount -t cifs -o username=hci,password=’Boonehci’ //PC4422/QSTESTING /mnt/pc4422/qstesting

04) On the Cloverleaf server: ln -s /mnt/pc4422/qstesting /data/win/qs/coldfeed_in

06) In the thread: set ibdir for the fileset-local protocol to /data/win/qs/coldfeed_in

06) In the thread: add the attached script (tpsScanDir.tcl) to fileset-local protocol with no arguments (grab all files in ibdir).

We use tpsScanDir.tcl in many, many threads for many years. It is known to work well; however, the samba mount to a Windows share is a new wrinkle. When a batch of files is placed in the Windows share, I can see the files from RedHat by doing ‘ls -al /data/win/qs/coldfeed_in/’. From the command line I can delete them, rename them, etc. The Cloverleaf fileset-local process does not “see” these files until I bounce the process. At this point, I do not know if it is an issue with the OS, Cloverleaf, or the tps proc.

Current file list:

-bash-3.2$ ll /data/win/qs/coldfeed_in/

total 1276

drwxrwxrwx 1 root root

-- Max Drown (Infor)

[Max Drown (Infor)]

To me, it looks like the process only sees the files if they are there before the process is bought up. If the files are put in the directory when the process is up, it never sees the files.

Note: It does see a new batch of file if I drop them in immediately after the first batch has been processed by Cloverleaf.

-- Max Drown (Infor)

[Max Drown (Infor)]

I tried the same process with no tps proc. I see the same behavior. Cloverleaf does not appear to see the files until the process is bounced.

Bouncing the thread also forces Cloverleaf to see the files. I have temporarily setup a cron job that bounces the thread every day.

At this point, I believe this to be a bug in Cloverleaf.

-- Max Drown (Infor)

[Max Drown (Infor)]

Apparently, Cloverleaf does not support Samba, or more likely, does not support cifs. However, this does not explain why Cloverleaf can see the files after the thread is bounced.

Support sent me a work-around for my fileset-local tps script that seems to be working good.

…
[code]…

-- Max Drown (Infor)

[Chuck Busch]

Max,

At what UPOC do you put this script.  Does it go

Protocol > Properties > Start-up procedures .

or

Does it go in the Outbound Tab > TPS Outbound Data

[Max Drown (Infor)]

Whatup, Chuck!?  😀

Are you running into a similar problem? This post was originally made in 2006, so much has changed in Cloverleaf since then.

-- Max Drown (Infor)

[Chuck Busch]

The problem I have is this.  I want to use Cloverleaf to transfer files from a server outside of our network to a cold feed in folder for HPF.  The VPN tunnel is built between Cloverleaf and the outside system.  I am not sure what the best way to proceed is.

1.  Should I create a share on my PWIM box for the sending system to drop files to.

 or  Should I try and FTP them from the outside server using my inbound thread.

2. Then for the outbound to the cold feed in directory.

  a. Should I use samba to mount a share to that directory or is there a different way to do this?

[Max Drown (Infor)]

Shoot me an email, and we’ll discuss some options.

-- Max Drown (Infor)

[Robert Denny]

Max, I do not know a whole lot about how Samba runs on the system, but we used to have it running on our system and we could do a fail over without any issue.

Now when we try to do a failover we are not able to run the cluster scripts because samba will not let go of the file system so that Lucy can run the script.

The error alludes to Samba running on the integrator share, but we used to not get that error. Is there a way to run samba on a different share?

[Max Drown (Infor)]

Robert, please place a ticket with support on Infor Xtreme.

-- Max Drown (Infor)

[Robert Denny]

I will do that. I had just filled out the form for access today, so I will put that in ASAP.

In the meantime I am asking the Server Admin who set it up if he knows of way to get samba to run on another share beside the Integrator.

I’ll post the outcome of this issue.

[Gene Millard]

I am having the same problem.  We have a mount point setup on our Linux box.  When files are put on the directory they just sit there until I bounce the thread. Then they process.  New files after that just sit there until the thread is bounced again. I am bouncing the thread several times a day because we are constantly receiving files.

Gene Millard

The Guthrie Clinic
Sayre, PA

[Author]

Replies