Nfs client ls /data/rw10 nfs client on mount: Permission denied

We are running an 800 cpu amd solaris 10 x64 cluster for HPC and an 512 cpu ultrasparc cluster solaris 10 for high
throughput.
Until now the nfs servers played ball and I did not experience real difficulties.
I am running two Solaris 10 x64 servers serving a total of 80 TB over nfs4, one Thumper serving 17 TByte over nfs4
and 7 linux serving 30 TByte over nfs3.
Today for the first time I got a massive rejection of mounts with the following error on the client.
May 9 18:24:10 m2001 nfs: [ID 664466 kern.notice] NFS compound failed for server c-store2: error 12 (RPC: Remote system error)
May 9 18:24:10 m2001 last message repeated 1 time
May 9 18:24:10 m2001 automountd[428]: [ID 834250 daemon.error] Mount of c-store2:/data2 on /data/rw10: I/O error
The load is not heavy by my standards as there are only 50 concurrent clients trying to mount that file space and the
same clients are mounting the thumper and do not get this problem.
I have had considerably heavier loads on the linux based nfs3 servers when 300 concurrent jobs were accessing one
file space at a time and I did not get this problem.
Have any of you seen this and found a remedy. any hints would be welcome

The problem solved itself mysteriously overnight, without any interference from myself.
The systems are again perfectly happily mounting the file space (650 clients of them all at the same time
mounting up to 6 filesystems from the same server) and the server is happily serving again as it has been for the past 2 years.
My idea is that there has been a network configuration clash, but considering that the last modification of NIS hosts file was about 4 weeks ago and the latest server was installed then and has been serving since then, I have no
idea how such clash could happen without interference in the config files. It is a mystery and I will have to make
every effort to unravel it. One does not really like to sweep incidents like that un-investigated under the carpet.
If anybody has any suggestions and thoughts on this matter please post them here.
Lydia

Similar Messages

Checking if NFS share is mounted on client

Hi
I would like to check on my nfs server if a nfs share is mounted on a client.
If I mount a share it is listed in /proc/fs/nfs/exports on the server, but it looks like it's not updated when the share is unmount; it still contains a line with the clients ip.

It looks like /var/lib/nfs/rmtab is the right file to check

OS X NFS not honoring group permission (again?)

I have a NFS appliance exporting an NFS share. It has group X configured, and folders owned by that group, and se to read/write/execute by the group.
On my Mac, I have created the same group, with the same GID. I then my user to that group (secondary group).
The Mac seems to think that my user does not belong to that group, because I get "Permission Denied" if I try to go into one of the directories in the Terminal. The Finder also shows the folder as locked. (Yes, I did try logging out, rebooting, etc.)
Anybody have any news about this problem? Looking around the support forums, it does not appear to be new. There are posts going back to 2008.
https://discussions.apple.com/message/9066836#9066836

Safe boot your computer.
Turn off computer. Hold shift key. Turn on computer. Keep holding shift. Once progress bar starts moving let go. If you can then login and use your computer it is not the OS it is some other application installed on the computer that is causing the issue.

Client host rejected: Access denied

Getting a ton of bounced back emails most likely the address is no longer in use but I filtered out any of the emails that say so. I'm no professional at this thats why I'm looking for help here. I tried searching for the problem on the forum but found
stuff about server 2003.
Im getting alot of the kickbacks saying Client host rejected: Access denied
I've tried emailing the recipient on my personal Gmail and recieved the same error. can we safely say that the addresses are no longer in use that i'm getting these kickbacks? heres the full header for anyone
who wants to look.
The original message was received at Wed, 5 Mar 2014 15:29:34 -0500 from odbmap07.extra.chrysler.com [129.9.107.35]
   ----- The following addresses had permanent fatal errors ----- <mail address here>
    (reason: 554 5.7.1 <unknown[151.171.97.83]>: Client host rejected: Access denied)
   ----- Transcript of session follows ----- ... while talking to odbmap07.out.extra.chrysler.com.:
<<< 554 5.7.1 <unknown[151.171.97.83]>: Client host rejected: Access denied
554 5.0.0 Service unavailable
We are using someone to host our email server for more information.
I use a program called G-Lock easy mail to send out our newsletter.

Hi,
Which email client are you using to send and receive emails? G-Lock?
Please refer to the links below and check if they help:
http://www.symantec.com/business/support/index?page=content&id=TECH169847
http://support.mailhostbox.com/email-administrators-guide/error-codes
In addition, if you are not using Microsoft Outlook as your email client, it's better to contact the support for your mail client for further assistance.
Best Regards,
Steve Fan
TechNet Community Support

Permission Denied on Solaris 10 NFS share, shared trough Windows Server 2008R2

Hello,
We have a NFS share on Windows Server 2008 R2 setup the following way,
NTFS permissions for ANONYMOUS LOGON and Everyone groups are set to Full control.
When mounting this share on our Solaris workstation, it mounts and we can view files in that mount but cannot edit or write to it.
mount -f nfs 10.0.0.2:/Folder/ /test
permissions are set as:
drwxrwxrwx 2 nobody nobody 4096 Mar 4 08:57 test/
when in test direcorie, trying to copy a file gives this error:
cp gp.txt gp_1.txt
cp: cannot create gp_1.txt: Permission denied
Please help,
Thanks

Hi,
Is there any error message in the Event Log on Windows Server 2008 R2? Please try to install the hotfix in the KB article below.
"Permission Denied" error when a UNIX user accesses files on an NFS share in Windows Server 2008 R2
http://support.microsoft.com/kb/2485529
Best Regards,
Mandy
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

After updating to Yosemite Server, one client now has Access Denied error on file sharing.

Just updated the law office from a Mavericks site to a Yosemite site. Everything is working fine except that one client now cannot connect to the file shares - Permission Denied, Contact your system administer error. I've looked through the permissions and even completed a Repair Permissions. What else can I do to get this client on-line with file sharing?

Is the client connecting with the same credentials as the others? I tend to doubt it.

Xsan client stopped mounting raid

Good Morning Community, I have xsan 2.2 and os 10.7.5
two of my clients stopped mounting the raid. they authenticate to the mdc but will not mount. erro on client says check fiber connections. i have switched computer with working connection and problem follows machine. xsan is working with all other machines only two. MDC system log shows
error mounting volume...operation coundn't be completed (SANTractionErrorDomain error 100007.) (100007)
any ideas? All help is greatly appreciated
thank you

Have you checked DNS and can the client receive a kerberose ticket? I know these don't sound relavant to a XSAN but after doing this for 8 years I can assure you it is.

DNS permission denied for vpn clients?

I have an x-serve setup to allow a client access remotely to a local network via VPN. I'm currently having an issue with the DNS server however, which is not allowing me to do lookups when connected via the VPN:
client 10.0.0.130#59551: view com.apple.ServerAdmin.DNS.public: error sending response: permission denied
The DNS server resolves perfectly fine for physical machines on the local network.

Have you added the range of VPN-assigned addresses to the list of clients the DNS server will respond to?
Server Admin -> (server) -> DNS -> Settings -> Accept recursive queries from the following networks
This will have to include the VPN client address range in order for the DNS server to respond to their queries.

70-Permission denied while importing data in a specific period for one location

Hi,
I've been working with FDM without any troubles for the past months, however when we try to import data to period (2013-01-01) in a specific location we keep on getting the 70-Permission denied error.
We've checked that the application has it's proper UNC path and the strange thing is that it all works perfectly fine with all the other periods in all location but not this period on this one location, we simply can't import data.
I have deleted the period and created it again but we keep on getting the error. I am about to delete the only location where we get the error and then create it again to see if this solves the problem.
Could anybody give me a clue of what could be the problem?
Thanks and regards
Santiago Ruiz

Has the location / period been locked? From memory i think the option to lock / unlock is in the tools menu option, based on location / period / category.

[Solved]NFS Client Not Mounting Shares

Here is my setup:
I have two Arch boxes that I am attempting to setup NFS shares on. The box that is going to be the server is headless FYI. So far, I have installed nfs-utils, started `rpc-idmapd` and `rpc-mountd` successfully on the server, and started `rpc-gssd` successfully on the client.
The folder I am trying to share is the /exports folder.
ls -l /exports
produces
total 8
drwxrwxrw-+ 110 daniel 1004 4096 Dec 6 17:26 Movies
drwxrwxrwx+ 13 daniel users 4096 Jan 8 19:12 TV-Shows
On the server:
/etc/exports
# /etc/exports
# List of directories exported to NFS clients. See exports(5).
# Use exportfs -arv to reread.
# Example for NFSv2 and NFSv3:
# /srv/home hostname1(rw,sync) hostname2(ro,sync)
# Example for NFSv4:
# /srv/nfs4 hostname1(rw,sync,fsid=0)
# /srv/nfs4/home hostname1(rw,sync,nohide)
# Using Kerberos and integrity checking:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt)
# /srv/nfs4/home gss/krb5i(rw,sync,nohide)
/exports 192.168.1.10(rw,fsid=0)
On the client:
showmount -e 192.168.1.91
Export list for 192.168.1.91:
/exports 192.168.1.10
Everything is looking hunky-dory. However, I go to mount using
sudo mount -t nfs4 192.168.1.91:/exports /mnt/Media
and the mount never takes place. It sits there and does nothing. I CAN, however, kill the process with Ctrl-c.
So does anybody have ANY idea why my shares aren't working.
EDIT: Just thought I should mention that all of the data in the /exports folder is a mount --bind from /mnt/media. All of the /mnt/media is contained on a USB external hard drive. I did notice that there is an ACL.
getfacl /exports
getfacl: Removing leading '/' from absolute path names
# file: exports/
# owner: root
# group: root
user::rwx
group::r-x
other::r-x
Last edited by DaBungalow (2014-01-10 03:18:05)

I found what the problem was. Apparently rpc_gssd was causing a problem. Stopping it fixed everything.

Solaris 10/08 w/ ZFS rpool NFS doesn't mount at boot time?

I've got an issue with NFS not mounting vfstab entered mounts during boot and was wondering if the latest Sol 10/08 with ZFS had anything to do with it.
1) #vi /etc/vfstab
server:/vol/share - /share nfs - yes rw,bg,hard,nointr,rsize=32768,wsize=32768,noac,vers=3,timeo=600
server2:/vol/share2 - /share2 nfs - yes rw,bg,hard,nointr,rsize=32768,wsize=32768,noac,vers=3,timeo=600
2) reboot -- -rv
Upon rebooting, the shares do not show up, but doing a mountall mounts them finally:
#mountall
mount: /tmp is already mounted or swap is busy
3) Doing a df -k at this point shows me they mounted.
So what gives? Why are they not mounting at boot? I tried to get around it by doing removing the vfstab entries, adding them into auto_master and then using cachefs, but my employer was not satisfied with autofs and wants them at boot and persistent via the vfstab. So what can be done to get this to work?
Thank you,
--tom

It appears I didn't have all of the services set online correctly:
#svcs |grep nfs
online Jan_05 svc:/network/nfs/status:default
online Jan_05 svc:/network/nfs/nlockmgr:default
So, I enabled the following:
#svcadm enable nfs/mapid
#svcadm enable nfs/cbd
#svcadm enable nfs/client
#scvs |grep nfs
Checked again:
#svcs |grep nfs
online Jan_05 svc:/network/nfs/status:default
online Jan_05 svc:/network/nfs/nlockmgr:default
online 15:48:24 svc:/network/nfs/mapid:default
online 15:48:33 svc:/network/nfs/cbd:default
online 15:48:42 svc:/network/nfs/client:default
Tested to make sure no errors were reported:
# svcs -xv
Then rebooted again.
Voila! It worked! Sometimes reading the documents on docs.sun.com pay off. I was just being too lazy to do it and gave up when I posted this. The solution is to check the services and ensure nfs/client is running correctly and then try rebooting again.

HOW TO: create NFS Archive log mount that runs parrallel

I would like to know if there is a way i can create an NFS mount that would run parallel Archiving and not stop if NFS mount is stale. If possible then how to create or configure?
Any and all help would be appreciated!
Edited by: 886101 on Sep 19, 2011 8:45 AM

On the server, edit the file <tt>/etc/exports</tt> to list the directories you
want NFS to offer, and to which systems they should be offered:
/u01    *(rw,sync,no_root_squash)
/u02    *(rw,sync,no_root_squash)
/u03    *(rw,sync,no_root_squash)The <tt>*</tt> matches any system/network and the <tt>(rw)</tt> says let the
other systems read and write the tree, the <tt>sync</tt> forces the server NFS
to finish the I/O before telling the clients the I/O is done, and the optional
<tt>no_root_squash</tt> lets root on a client system access the files as if
they were root on the NFS server; this may not be what you want.
# /sbin/chkconfig nfs on
# /sbin/service nfs startOn the NFS client, edit the <tt>/etc/fstab</tt> file to have lines that look
like this:
myserver:/u01 /u01 nfs rw,rsize=32768,wsize=32768,sync,nointr,hard 0 0
myserver:/u02 /u02 nfs rw,rsize=32768,wsize=32768,sync,nointr,hard 0 0
myserver:/u03 /u03 nfs rw,rsize=32768,wsize=32768,sync,nointr,hard 0 0and then from the client make sure you can see the offered files:
# /usr/sbin/showmount -e myserverand if you can, do this on the client:
# mkdir /u01 /u02 /u03
# mount /u01
# mount /u02
# mount /u03If the clients ever reboot, the NFS files will be mounted automatically and you
will not need these last 3 commands.
The RDBMS has its own requirements for the options in the <tt>/etc/fstab</tt>
entry, so the <tt>rw,rsize=...</tt> example may need to be adjusted a little.
Happy NFS'ing.

NFS4-with-Kerberos client stopped mounting

This was working fine till several days ago. Then I started getting:
mount.nfs: access denied by server while mounting <server>:<share>
Looking in the journal found this:
kernel: rpc.gssd[11749]: segfault at 1 ip 00007f036db91d75 sp 00007fffbb5b9df0 error 4 in libgssglue.so.1.0.0[7f036db8e000+9000]
systemd[1]: rpc-gssd.service: main process exited, code=dumped, status=11/SEGV
systemd[1]: Unit rpc-gssd.service entered failed state.
systemd-coredump[11764]: Process 11749 (rpc.gssd) dumped core.
Without rpc.gssd operating, no wonder the mount fails.
On suspicion of a recent upgrade breaking something, I downgraded:
- nfs-utils from 1.2.8-3 to 1.2.7-1
- libtirpc from 0.2.3-1 to 0.2.2-4
- rpcbind from 0.2.0-11 to 0.2.0-8
Those were all updated on May-10-2013. After downgrading, NFS mounting works normally again on the client.
EDIT: Reported as bug https://bugs.archlinux.org/task/35327
Last edited by Cassino (2013-05-16 15:48:43)

This was working fine till several days ago. Then I started getting:
mount.nfs: access denied by server while mounting <server>:<share>
Looking in the journal found this:
kernel: rpc.gssd[11749]: segfault at 1 ip 00007f036db91d75 sp 00007fffbb5b9df0 error 4 in libgssglue.so.1.0.0[7f036db8e000+9000]
systemd[1]: rpc-gssd.service: main process exited, code=dumped, status=11/SEGV
systemd[1]: Unit rpc-gssd.service entered failed state.
systemd-coredump[11764]: Process 11749 (rpc.gssd) dumped core.
Without rpc.gssd operating, no wonder the mount fails.
On suspicion of a recent upgrade breaking something, I downgraded:
- nfs-utils from 1.2.8-3 to 1.2.7-1
- libtirpc from 0.2.3-1 to 0.2.2-4
- rpcbind from 0.2.0-11 to 0.2.0-8
Those were all updated on May-10-2013. After downgrading, NFS mounting works normally again on the client.
EDIT: Reported as bug https://bugs.archlinux.org/task/35327
Last edited by Cassino (2013-05-16 15:48:43)

Kanaka Client unable Mount volume

I have OES11SP2 on SLES 11 SP3 on which I am running KANAKA ENGINE to mount volumes on MAC Client from servers running under same Tree.
Created eDirectory user account which have rights on volumes from two servers under the same tree.
example: 1) abc (volume) under Server1 (Running Kanaka engine)
2) xyz (volume) under Server2
Note: Tested AFP connectivity working without issues for both the volumes from MAC OS, also eDirectory users can map both volumes on windows machine with Novell client login.
Issue is I cannot mount volume from Server2 using KANAKA Client on MAC OS. However Server1(running kanaka engine) can able to mount.
any help is highly appreciated.

01 2014-12-14 20:03:42 10800 1 0001 13780 7f5258c2c760 Engine::SignalHandler() - Invoked. Signal = {SIGTERM} 15.
01 2014-12-14 20:03:45 10800 5 0001 13780 7f524e92d700 WD: Engine mainline thread is leaving the Watch Dog function...
82 2014-12-14 20:03:45 10800 0 ff08 13780 7f524e12c700 <CONFIG><LEVEL>5</LEVEL><CATEGORY/></CONFIG>
82 2014-12-14 20:03:45 10800 0 ff09 13780 7f524e12c700 <CONFIG><LEVEL>5</LEVEL><CATEGORY/></CONFIG>
01 2014-12-14 20:03:45 10800 5 0001 13780 7f524e92d700 ML: Engine is shutting down...
01 2014-12-14 20:03:45 10800 5 0001 13780 7f524e92d700 ML: Terminating the HTTPx Server subsystem...
01 2014-12-14 20:03:45 10800 5 0001 13780 7f524e92d700 ML: Terminating the User Index Manager subsystem...
01 2014-12-14 20:03:45 10800 5 0007 13780 7f524e92d700 Index Manager: Shutting Down...
01 2014-12-14 20:03:45 10800 5 0007 13780 7f524e92d700 Index Manager: Waiting for Scheduler Thread to Terminate...
01 2014-12-14 20:03:46 10800 5 0007 13780 7f524e92d700 Index Manager: Waiting for All Worker Threads to Terminate...
01 2014-12-14 20:03:46 10800 5 0007 13780 7f524e92d700 Index Manager: Shut Down Complete...
01 2014-12-14 20:03:46 10800 5 0001 13780 7f524e92d700 ML: Configuring the Novell XPLAT environment to no longer perform logging...
01 2014-12-14 20:03:46 10800 5 0001 13780 7f524e92d700 ML: Saving state information...
01 2014-12-14 20:03:46 10800 5 0001 13780 7f524e92d700 ML: Saving the Salt state information...
01 2014-12-14 20:03:46 10800 5 0001 13780 7f524e92d700 ML: Saved the Salt state information, bResult = 1.
01 2014-12-14 20:03:46 10800 5 0001 13780 7f524e92d700 ML: Completed saving state information, bOK = 1.
01 2014-12-14 20:03:46 10800 5 0001 13780 7f524e92d700 ML: Engine has shut down. Thread is terminating...
01 2014-12-14 20:03:46 10800 0 8001 13780 7f524e12c700 Shutting down the Logger. Closing log file "/var/opt/novell/kanaka/engine/log/novell-kanakaengined-20141202-132804.log".
81 2014-12-14 20:03:46 10800 0 8001 13780 7f524e12c700 <LOGFILECLOSE/>
81 2014-12-14 20:03:49 10800 0 8001 10919 7f517cb27700 <LOGFILEOPEN/>
81 2014-12-14 20:03:49 10800 0 8001 10919 7f517cb27700 <LOGGER><VERSION>1</VERSION><APPNAME>novell-kanakaengined</APPNAME><TZBIAS>10800</TZBIAS><OSVERSIONINFO>Kernel Name: Linux, Architecture: x86_64, Kernel Release: 3.0.76-0.11-default, Kernel Version: #1 SMP Fri Jun 14 08:21:43 UTC 2013 (ccab990), Machine HW Name: x86_64</OSVERSIONINFO><OSBITS>64</OSBITS><APPBINARYFILESPEC>/opt/novell/kanaka/engine/bin/novell-kanakaengined</APPBINARYFILESPEC><APPBITS>64</APPBITS><AppVersion/><PROCESSID>10919</PROCESSID><THREADID>139987961149184</THREADID><LOGFILEPARAMS><ROLLOVERTYPE>2</ROLLOVERTYPE><FILESTORETAIN>10</FILESTORETAIN><FILESIZEMAX>10485760</FILESIZEMAX></LOGFILEPARAMS><LOGLEVELNAMEMAP><ENTRY><LEVEL>0</LEVEL><NAME>Logging Disabled</NAME></ENTRY><ENTRY><LEVEL>1</LEVEL><NAME>Fatal</NAME></ENTRY><ENTRY><LEVEL>2</LEVEL><NAME>Critical</NAME></ENTRY><ENTRY><LEVEL>3</LEVEL><NAME>Error</NAME></ENTRY><ENTRY><LEVEL>4</LEVEL><NAME>Warning</NAME></ENTRY><ENTRY><LEVEL>5</LEVEL><NAME>Informational</NAME></ENTRY><ENTRY><LEVEL>6</LEVEL><NAME>Success</NAME></ENTRY><ENTRY><LEVEL>7</LEVEL><NAME>Verbose</NAME></ENTRY><ENTRY><LEVEL>8</LEVEL><NAME>Debug</NAME></ENTRY></LOGLEVELNAMEMAP><CATEGORYNAMEMAP><ENTRY><CATEGORY> 1</CATEGORY><NAME>Engine Watchdog</NAME></ENTRY><ENTRY><CATEGORY>3</CATEGORY><NAME>Engine Global Class</NAME></ENTRY><ENTRY><CATEGORY>4</CATEGORY><NAME>UI Session Manager</NAME></ENTRY><ENTRY><CATEGORY>5</CATEGORY><NAME>Web UI Session Manager</NAME></ENTRY><ENTRY><CATEGORY>6</CATEGORY><NAME>Client Manager</NAME></ENTRY><ENTRY><CATEGORY>7</CATEGORY><NAME>Index Manager</NAME></ENTRY><ENTRY><CATEGORY>8</CATEGORY><NAME>Login Script Parser</NAME></ENTRY><ENTRY><CATEGORY>32769</CATEGORY><NAME>Logger</NAME></ENTRY><ENTRY><CATEGORY>32770</CATEGORY><NAME>FSTools</NAME></ENTRY><ENTRY><CATEGORY>32771</CATEGORY><NAME>DSTools</NAME></ENTRY><ENTRY><CATEGORY>32772</CATEGORY><NAME>HTTPxServer</NAME></ENTRY><ENTRY><CATEGORY>32773</CATEGORY><NAME>HTTPxClient</NAME></ENTRY><ENTRY><CATEGORY>32774</CATEGORY><NAME>TaskMgr</NAME></ENTRY><ENTRY><CATEGORY>32775</CATEGORY><NAME>NWXPlat</NAME></ENTRY><ENTRY><CATEGORY>32776</CATEGORY><NAME>Storage Resources</NAME></ENTRY><ENTRY><CATEGORY>32777</CATEGORY><NAME>Security</NAME></ENTRY><ENTRY><CATEGORY>32778</CATEGORY><NAME>Thread</NAME></ENTRY><ENTRY><CATEGORY>32779</CATEGORY><NAME>OS Util</NAME></ENTRY><ENTRY><CATEGORY>32780</CATEGORY><NAME>Scheduling Service</NAME></ENTRY></CATEGORYNAMEMAP><LOGFILELOGLEVELMAP><ENTRY><CATEGO RY>0</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>1</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>3</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>4</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>5</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>6</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>7</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>8</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32769</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32770</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32771</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32772</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32773</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32774</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32775</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32776</CATEGORY><LEVEL>5</LEVEL></ENTRY></LOGFILELOGLEVELMAP><CONERRLOGLEVELMAP><ENTRY><CATE GORY>0</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>1</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>3</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>4</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>5</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>6</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>7</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>8</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32769</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32770</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32771</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32772</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32773</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32774</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32775</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32776</CATEGORY><LEVEL>5</LEVEL></ENTRY></CONERRLOGLEVELMAP><SYSLOGLOGLEVELMAP><ENTRY><CATEG ORY>0</CATEGORY><LEVEL>2</LEVEL></ENTRY><ENTRY><CATEGORY>1</CATEGORY><LEVEL>2</LEVEL></ENTRY><ENTRY><CATEGORY>3</CATEGORY><LEVEL>2</LEVEL></ENTRY><ENTRY><CATEGORY>4</CATEGORY><LEVEL>2</LEVEL></ENTRY><ENTRY><CATEGORY>5</CATEGORY><LEVEL>2</LEVEL></ENTRY><ENTRY><CATEGORY>6</CATEGORY><LEVEL>2</LEVEL></ENTRY><ENTRY><CATEGORY>7</CATEGORY><LEVEL>2</LEVEL></ENTRY><ENTRY><CATEGORY>8</CATEGORY><LEVEL>2</LEVEL></ENTRY><ENTRY><CATEGORY>32769</CATEGORY><LEVEL>2</LEVEL></ENTRY><ENTRY><CATEGORY>32770</CATEGORY><LEVEL>2</LEVEL></ENTRY><ENTRY><CATEGORY>32771</CATEGORY><LEVEL>2</LEVEL></ENTRY><ENTRY><CATEGORY>32772</CATEGORY><LEVEL>2</LEVEL></ENTRY><ENTRY><CATEGORY>32773</CATEGORY><LEVEL>2</LEVEL></ENTRY><ENTRY><CATEGORY>32774</CATEGORY><LEVEL>2</LEVEL></ENTRY><ENTRY><CATEGORY>32775</CATEGORY><LEVEL>2</LEVEL></ENTRY><ENTRY><CATEGORY>32776</CATEGORY><LEVEL>2</LEVEL></ENTRY></SYSLOGLOGLEVELMAP><EVENTLOGLOGLEVELMAP><ENTRY><CAT EGORY>0</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>1</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32769</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32770</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32771</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32772</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32773</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32774</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32775</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32776</CATEGORY><LEVEL>0</LEVEL></ENTRY></EVENTLOGLOGLEVELMAP><DEBUGPORTLOGLEVELMAP><ENTRY>< CATEGORY>0</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>1</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32769</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32770</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32771</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32772</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32773</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32774</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32775</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32776</CATEGORY><LEVEL>0</LEVEL></ENTRY></DEBUGPORTLOGLEVELMAP><SYSLOGPARAMS><SYSLOGLEVEL>1</SYSLOGLEVEL><SYSLOGFACILITY>1</SYSLOGFACILITY><SYSLOGLEVELMAP><ENTRY><LEVEL>1</LEVEL><PRIORITY>2</PRIORITY></ENTRY><ENTRY><LEVEL>2</LEVEL><PRIORITY>2</PRIORITY></ENTRY><ENTRY><LEVEL>3</LEVEL><PRIORITY>3</PRIORITY></ENTRY><ENTRY><LEVEL>4</LEVEL><PRIORITY>4</PRIORITY></ENTRY><ENTRY><LEVEL>5</LEVEL><PRIORITY>5</PRIORITY></ENTRY><ENTRY><LEVEL>6</LEVEL><PRIORITY>5</PRIORITY></ENTRY><ENTRY><LEVEL>7</LEVEL><PRIORITY>6</PRIORITY></ENTRY><ENTRY><LEVEL>8</LEVEL><PRIORITY>7</PRIORITY></ENTRY></SYSLOGLEVELMAP></SYSLOGPARAMS><EVENTLOGPARAMS><EVENTLOGTYPE>0</EVENTLOGTYPE><EVENTLOGTYPEMAP/></EVENTLOGPARAMS></LOGGER>
01 2014-12-14 20:03:49 10800 0 8001 10919 7f517cb27700 Initializing Logger, re-opening existing log file "/var/opt/novell/kanaka/engine/log/novell-kanakaengined-20141202-132804.log".
01 2014-12-14 20:03:49 10800 0 8001 10919 7f517cb27700 This Logger class instance [0xadae90] was initialized at 2014:12:14:20:03:49 in Process ID # 10919.
01 2014-12-14 20:03:49 10800 0 8001 10919 7f517cb27700 OS Version Info = "Kernel Name: Linux, Architecture: x86_64, Kernel Release: 3.0.76-0.11-default, Kernel Version: #1 SMP Fri Jun 14 08:21:43 UTC 2013 (ccab990), Machine HW Name: x86_64", OS Bits = 64, Application binary file spec = "/opt/novell/kanaka/engine/bin/novell-kanakaengined", Application Bits = 64, Application Version = "".
01 2014-12-14 20:03:49 10800 0 8001 10919 7f517cb27700 This is the first time that a Logger thread has been started for this class instance.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Thread has started.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Configuring the client logging subsystem [Phase I]...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Completed configuring the client logging subsystem [Phase I], bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Getting Operational Data [Phase I]...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Engine's instance name = "".
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Engine is getting configuration path information...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Engine completed getting configuration path information, Result = 0, bOK = 1, path = "/etc/opt/novell/kanaka/engine/config".
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Engine is getting program path information...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Engine completed getting program path information, bOK = 1, path = "/opt/novell/kanaka/engine/bin".
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Completed getting Operational Data [Phase I], bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Initializing the Configuration...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Setting the reports data path...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Completed setting the reports data path, sPathSpec = "/var/opt/novell/kanaka/engine/data/reports", bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Setting the rtconfig reports data path...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Completed setting the rtconfig reports data path, sPathSpec = "/var/opt/novell/kanaka/engine/data/reports/rtconfig", bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Setting the client log data path...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Completed setting the client log data path, sPathSpec = "/var/opt/novell/kanaka/engine/log/client", bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Validating data path information...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Completed validating data path information, Data Path = "/var/opt/novell/kanaka/engine/data", bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Completed initializing the Configuration, bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Configuring the Logging subsystem [Phase II]...
82 2014-12-14 20:03:49 10800 0 ff04 10919 7f517cb27700 <CONFIG><LOGPATH>/var/opt/novell/kanaka/engine/log</LOGPATH></CONFIG>
82 2014-12-14 20:03:49 10800 0 ff05 10919 7f517cb27700 <CONFIG><LOGFILEBASENAME/></CONFIG>
82 2014-12-14 20:03:49 10800 0 ff05 10919 7f517cb27700 <CONFIG><LOGFILEBASENAME>novell-kanakaengined</LOGFILEBASENAME></CONFIG>
82 2014-12-14 20:03:49 10800 0 ff08 10919 7f517cb27700 <CONFIG><LEVEL>5</LEVEL><CATEGORY/></CONFIG>
82 2014-12-14 20:03:49 10800 0 ff07 10919 7f517cb27700 <CONFIG><ROLLOVERTYPE>2</ROLLOVERTYPE><FILESTORETAIN>10</FILESTORETAIN><FILESIZEMAX>10485760</FILESIZEMAX></CONFIG>
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Completed configuring the Logging subsystem [Phase II], bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Completed configuring the client logging subsystem [Phase II], bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Getting Operational Data [Phase II]...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Setting the XML Message Signature object...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Completed setting the XML Message Signature object, bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Setting the SSL/TLS certificate file...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Completed setting the SSL/TLS certificate file, sFileSpec = "/etc/opt/novell/kanaka/engine/config/server.pem", bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Setting the storage resources file...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Completed setting the storge resources file, sFileSpec = "/var/opt/novell/kanaka/engine/data/storage-resources.dat", bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Setting the user index file...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Completed setting the user index file, sFileSpec = "/var/opt/novell/kanaka/engine/data/userindex.dat", bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Setting the client list file...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Completed setting the client list file, sFileSpec = "/var/opt/novell/kanaka/engine/data/clients.dat", bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Engine is determining its own DNS host name...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Engine completed determining its own DNS host name, Result = 0, bOK = 1, Name = "kanakasrvkaia".
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Engine completed determining its own DNS host name, Result = 0, bOK = 1, Name = "kanakasrvkaia".
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Engine is getting O.S. version information...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Engine completed getting O.S. version information, Result = 0, bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Engine is getting file version information for itself ["/opt/novell/kanaka/engine/bin/novell-kanakaengined"]...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Engine completed getting file version information for itself ["/opt/novell/kanaka/engine/bin/novell-kanakaengined"], Version = "2.7.1.8", Result = 0, bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Completed getting Operational Data [Phase II], bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Getting Operational Data [Phase III]...
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Engine is finished preparing DS Context, eDir Tree Name = "KTREE", Result = 0, bOK = 1.
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Completed getting Operational Data [Phase III], bOK = 1.
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Configuring the Novell XPLAT environment to perform logging...
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Completed configuring the Novell XPLAT environment to perform logging, bOK = 1.
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Initializing the HTTPx Server subsystem...
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Completed initializing the HTTPx Server subsystem, bOK = 1.
82 2014-12-14 20:03:51 10800 0 ff08 10919 7f517cb27700 <CONFIG><LEVEL>5</LEVEL><CATEGORY/></CONFIG>
82 2014-12-14 20:03:51 10800 0 ff09 10919 7f517cb27700 <CONFIG><LEVEL>5</LEVEL><CATEGORY/></CONFIG>
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Loading saved state information...
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Loading the Salt state information...
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Loaded the Salt state information, bOK = 1.
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Completed loading state information, bOK = 1.
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Successfully authenticated as the Proxy Account.
01 2014-12-14 20:03:51 10800 5 0003 10919 7f517d328700 GL: Base schema appears to be properly extended.
01 2014-12-14 20:03:51 10800 5 0003 10919 7f517d328700 GL: Collaborative Homedirectory attribute ccx-FSFManagedPath is available.
01 2014-12-14 20:03:51 10800 5 0003 10919 7f517d328700 GL: Kanaka AFP Volume name attribute cccKanakaAFPVolumeName is available.
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Attempted validate accounts, Result = 0.
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Successfully authenticated as the Proxy Account.
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Attempted to Generate new SALT and Proxy Password, Result = 0.
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Called LoadStorageResourcesFromCache(), Result = 0.
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Called LoadClientManager(), Result = 0.
01 2014-12-14 20:03:51 10800 3 0001 10919 7f517d328700 ML: Called LoadMountPointManager(), Result = 53.
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Called LoadIndexManager(), Result = 0.
01 2014-12-14 20:03:51 10800 5 0007 10919 7f517d328700 Index Manager: Starting Scheduler Thread...
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Called IndexManager::StartIndexingScheduler(), Result = 0.
01 2014-12-14 20:03:51 10800 5 0007 10919 7f517991c700 Index Manager [ST]: Next User Index Rebuild will happen in 14169 seconds.
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Called LoadKanakaPolicy(), Result = 0.
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Starting the HTTPx Server subsystem...
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Completed starting the HTTPx Server subsystem, bResult = 1.
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Completed initialization. Engine is now running.
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 WD: Engine mainline thread is entering the Watch Dog function...
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 WD: Engine is running...
01 2014-12-14 20:04:50 10800 5 0004 10919 7f5172c9f700 UI: admin.kaia [192.168.1.180] LOGIN SUCCESS

Can a Web Start application run on client without write permission?

Hello,
we have a customer who operates a large number of Windows clients with an installed Java applications on it. The installation can only be done by an administrator, because the users have only write permission on temp directories and are not allowed to install something on their own. This of course leads to long rollout phases of new software releases.
That's why we thought about deploying the application via Web Start, but we don't have experience in that field yet. But we assume that this would be the best way to go, since porting it to a browser-based web application is not easy due to the rich client gui.
So my question is - can Web Start operate in such a scenario, where there is only write permission on temp directories for the user?
By operating I mean the deployment and starting of the application - the application itself does not have to write anything on disk.
Thanks for any help,
regards, Geziefer

..the users have only write permission on temp directories ..Can the location of the Java cache be set to those temp directories by the administrator?

Nfs client ls /data/rw10 nfs client on mount: Permission denied

Similar Messages

Maybe you are looking for