Linux WinCC and Samba share problem

[CyaNn]

Hello folks,

I have a stucking problem with a share between a Windows NAS and CentOS

Configuration :
CentOS 6.4 (Final)
WinCC 3.10-SP2

I mounted a share from centos system to our enterprise NAS, here is the command line I used:

Code: Select all

sudo mount -t cifs //156.135.81.40/isup -o 'username=****,password=****,rw,nounix,iocharset=utf8,uid=administrator,gid=wheel,file_mode=0777,dir_mod=0777' /mnt/w

The mount point is ok through CentOS nautilus and shell, I can explore share, create and delete file and directories (right are actually very extended for testing)

But it does not works with our WinCC project as proj_path, here is an extract of our config file :

Code: Select all

proj_path="/opt/WinCC_OA/3.10"
proj_path="/mnt/w/sgFw"             # does not works
proj_path="/mnt/w/sgCommon"    # does not works
proj_path="/project/winccoa/EMSup_G"

But through the project administrator it does not works, here is the log extract :

Code: Select all

"PVSS00pmon [/project/winccoa/EMSup_G/config/config]": proj_path nonexistent, inaccessible or not a directory: /mnt/w/sgFw
"PVSS00pmon [/project/winccoa/EMSup_G/config/config]": proj_path nonexistent, inaccessible or not a directory: /mnt/w/sgCommon
PVSS00pmon    (1), 2017.10.04 08:45:13.802: exit(1) called!

Even if I tried to launch the console as root and after a lots of right tuning.... nothing works !!!!

Please help me..... I am really stuck and it is mandatory for us to use this share.

[leoknipp]

If you start the command in a shell the mountpoint is maybe only valid in that shell and therefore it does not work when starting the process monitor from another shell.

Can you access the shared directory within a new opened shell?
Does it work when you start WCCILpmon in the shell where you have made the mounts?

Best Regards
Leopold Knipp
Senior Support Specialist

[agruber]

In addition to the hints above I noticed you mount using CIFS.

I strongly recommend using mountpoints which support case sensitive file/directory names. Because that is what WinCC OA expects when being used in Linux, which is of course also case sensitive. This could also be the reason or part of the reason for your problem.

BR, Andreas
Customer Care

[CyaNn]

Hello, thank you for the answer.
I have tried to use fstab to configure during boot, and it does not works anymore.
The mount point work perfectly on every linux tools except WinCCoa

[CyaNn]

Hello Andreas, thank you a lot for your response.
What mountpoint can works with a Windows share in non sensitive way ?

I will verify the case, but I think it is ok in this side.

[agruber]

Since Windows is not case sensitive a Windows share can always cause issues in Linux.

You can try to copy your projects from the share with a simple "cp -R /mnt/w/sgFw /home/" and try if it works after a copy from that share directly on the destination machine.

On a sidenote, WinCC OA 3.10.2, which itself is unsupported for years, was never tested on CentOS 6. So expect other problems too.

I suggest to upgrade WinCC OA and CentOS to the newest version, especially if you plan to do bigger changes or additions to your project. Or is there a particular reason for using this old version?

BR, Andreas
Customer Care

[CyaNn]

Many thanks Andreas,

By copying the share to a local folder and changing the config file accordingly it works perfectly (as expected).
A also tried to create an Alias, but it does not works, this time.

About the WinCC version, I also experienced some huge problèmes with EWO developpements.
Well, we have planned to migrate to WinCC3.15 for the next year. But while waiting, I have to find a workround.