NFS-e

Bom dia.
Ouvi falar hoje de uma tal de Nota Fiscal de Serviço Eletrônica (NFS-e).
Vai existir alguma coisa no GRC para recepcionar estas notas?
Obrigado.
At.,
Bernardo Tavares Braga

Bernardo,
existe sim a intencao da SAP de analisar o assunto assim que ele vire um padrão nacional.
Infelizmente, por enquanto há apenas a definicao de um padrão de processo/layout mas não há um comprometimento das prefeituras em seguir esse padrao.
Belo Horizonte é hoje a unica capital que está seguindo. Sao Paulo tem seu proprio layout, e as demais capitais estao cada uma com seu proprio planjemaneto.
A SAP só tem condicoes de estudar a possibilidade de prover uma solucao standard quando houver um comprometimento das prefeituras em seguir o padrao nacional, no mesmo modelo que houve p/ a NF-e de Mercadorias (modelo 55), onde todas as SEFAZs do Brasil assinaram a lei que a define. Se nao houver esse comprometimento, a SAP nao tem intencao de disponibilizar uma solucao que atenda parcialmente, nem condicoes de disponibilizar diversas solucoes, uma para cada prefeitura.
A tendencia é que tenhamos novidades sobre esse assunto em 2010; vamos esperar.
Att,
Henrique.

Similar Messages

Vi error on nfs mount; E212: Can't open file for writing

Hi all,
I've setup a umask of 0 for testing on both NFS client (Centos 5.2) and NFS server (OSX 10.5.5 server).
I can create files as one user and edit/save out as another user w/o issue when directly logged into the server via ARD.
However, when I attempt the same from an NFS mount on a client machine, even as root I get the following error using vi;
"file" E212: Can't open file for writing
Looking at the system.log file on the server, I see;
kernel[0]: add_fsevent: no name hard-link! dropping the event. (event 2 vp == 0xa5db510 (-UNKNOWN-FILE)).
This baffles me. My umask is 0 meaning files I create and attempt to edit as other users are 777, but I cannot save out edits unless I do a wq! in vi. At that point, the owner of the file changes to whomever did the vi.
This isn't just a vi issue as it happens using any editor, but I like to use vi.
Any help is greatly appreciated. Hey, beer is on me!

Hi all,
Thanks for the replies
I've narrowed it down to a Centos client issue.
Everything works fine using other Linux based OS's as clients.
Since we have such a huge investment in Centos, I must figure out a workaround. Apple support wasn't much help as usual however they were very nice.
There usual response is "its unsupported".
If Apple really wants to play in the enterprise of business space, they really need to change there philosophy. I mean telling me that I shouldn't mount home directories via NFS is completely rediculus.
What am I supposed to use then, Samba of AFP? No, I don't think so. No offense to Microsoft but why would I use a Windows based file sharing protocol to mount network shares in a Nix env???

10.6.2 failed to install due to 'nfs error', audio no longer works

macbook pro, all other updates have installed just fine, except for 10.6.2
I get this in the log:
11/10/09 3:58:15 PM com.apple.kextcache410 Created mkext archive //System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext.
11/10/09 3:58:15 PM com.apple.kextcache403 Failed to mount helper partition: error 0XF8DA000C (DA err# 0x0c).
11/10/09 3:58:15 PM com.apple.kextd10 kextcache error while updating / (error count: 4)
11/10/09 3:58:15 PM com.apple.kextcache403 /: trouble updating one or more helper partitions.
11/10/09 3:58:15 PM com.apple.kextd10 async child pid 403 exited with status 70
11/10/09 3:58:15 PM com.apple.kextd10 kextcache error while updating / (error count: 5)
11/10/09 3:58:15 PM installd376 PackageKit: Install Failed: (null)
Error Domain=PKInstallErrorDomain Code=121 UserInfo=0x104d22740 "An error occurred while updating system extension information." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=70 "The operation couldn’t be completed. Stale NFS file handle") {
NSLocalizedDescription = "An error occurred while updating system extension information.";
NSUnderlyingError = "Error Domain=NSPOSIXErrorDomain Code=70 \"The operation couldn\U2019t be completed. Stale NFS file handle\"";
arguments = (
"-update-volume",
nothing is mounted (i rebooted before applying). not sure why it's giving that NFS error. it's consistent tho.. if i reboot and try the manual install of the patch, I get the same error.
after the failed patch "installed" it left my sound not working... so far everything else appears to work. any thoughts on fixing this are appreciated. i ran diskutil and 'fixed perms' and 'verified disk' ... patch still fails.

Try reinstalling the patch. If you get all the way through the installation, then see if your sound works. If not, then I suggest you do a repair install of Sno by installing Sno over Sno as in an upgrade install. Such an install, while usually very safe, still is an install so be appropriated backed up if you proceed.

Local vs NFS disk access

We're buying a new platform for our Oracle server. It'll be...
(4) 1.3ghz 64 bit (Madisons)
48gb memory
(2) 36gb drives - For OS and Swap
(2) 146gb drives - For general work space
The question is where to put the disks that will contain the database proper. There will be only one Oracle server associated with the data on these disks. This is not a distributed DB application of any kind. It is a single server app having sole access to it's data disks.
Our IS group is proposing to use NAS (network attached storage) like a netapp filter which would provide NFS access via it's own OS. Access to the filter would be via 1 or more copper gigabyte connections. The network itself wiould be shared by other users in a large engineering group.
The alternative is to mount the disks directly onto the server itself... no network.
My concern is that the networked approach will be noticably slower than the local mount, especially where network loads can be unpredictable and heavy at times in the engineering group at large. But I have no experience or data to support the fear that it'll be ~that~ much slower.
The activity on our DB is...
DB loading done by C/SQL programs loading large volumes of data, all day long.
DB reads also done by DB loaders (as part of their normal operation) but most important, end users query during normal work hours with many moderately sized queries involving several table joins and retrieval of perhaps a few hundred records.
Does anyone have any experience the performance differences between locally mounted RAID arrays and networked disks?
Does anyone have any before/after stats that may shed some light on what we can expect in the area of performance degredation?
P.S. I had previously posted this message in "Database General" but expect that it should have been posted here in stead.

Just out of Morbid Curiousity- If you get info on those Firewire drives- do they have the "ignore Permissions...." box checked.

Problem with NFS in sender file adapter

Hi everybody,
I´m facing the following problem.
The XI runs under a HP-UNIX server and I want to access into a windows server by using NFS in the file sender adapter.
I have created a shared folder in the windows server.
In the Source Directory field I have typed: //Windows_Server/Shared_folder.
In the file name field: FileA.txt
The error is the following:
History:
- 2006-11-24 13:16:41 CET: Retry interval started. Length: 10.000 s
- 2006-11-24 13:16:41 CET: Error: Directory //Windows_Server/Shared_folder does not exist
- 2006-11-24 13:16:41 CET: Processing started
Do I need to do anything else?
Any idea?
Thanks
Carlos

hi,
can you access the folder when you're logged onto the HP-UNIX server?
with this path //Windows_Server/Shared_folder.
(via console for example) ?
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Dúvida no Preenchimento dos campos PREFNO / CHECOD em NFS-e de SP

Olá Pessoal,
Estou a procura de informações sobre a solução para nota fiscal eletronica de serviços da prefeitura de São Paulo, pesquisando no forum pouco encontrei sobre a nota 981687 - NFe: For Services in Muncipio Sao Paulo.
A SAP disponibilizou os dois campos PREFNO / CHECOD para o numero da nota fiscal e código de verificação gerados pela prefeitura (uma vez que o SAP deve gerar o número da RPS), além de um report para geração do arquivo TXT e envio manual.
Minha dúvida é a seguinte:
1) Após enviar o arquivo para a prefeitura, são convertias as RPS em Notas Fiscais Eletronicas. Como armazenar as informações nos campos standards mencionados ? Existe um outro report que le o arquivo de retorno da prefeitura ?
Outra dúvida está na procura de uma sugestão, onde o RPS pode ter até 12 posições e o NFNUM do SAP apenas 6. Vcs estão utilizando outro campo Z para compor o numero maior ? Ou como esta fazendo quando o RPS atingir 999.999 ? Pensei en usar o NFENUM, mas teria o mesmo problema quando atingir o limite de 9 posições (999.999.999).
Muito obrigado pela atenção e ajuda.

A_cristovao ,
Vamos ver se posso lhe ajudar em algo:
1) Após enviar o arquivo para a prefeitura, são convertias as RPS em Notas Fiscais Eletronicas. Como armazenar as informações nos campos standards mencionados ? Existe um outro report que le o arquivo de retorno da prefeitura ?
Resposta: Em alguns projetos que passei, consultei os abaps e sempre foi desenvolvido um programa Z para ler este arquivo e fazer um BDC na J1B2N, porem sua categoria de nota não dever ser eletrônica, aqueles dois campos flag no cabeçalho NF eletronica e NF servico, apenas o último(serviço) marcado para o BDC entrar e conseguir mapear o campo com o NFSe e cod verificador.
2) Outra dúvida está na procura de uma sugestão, onde o RPS pode ter até 12 posições e o NFNUM do SAP apenas 6. Vcs estão utilizando outro campo Z para compor o numero maior ? Ou como esta fazendo quando o RPS atingir 999.999 ? Pensei en usar o NFENUM, mas teria o mesmo problema quando atingir o limite de 9 posições (999.999.999).
Resposta: Esse estamos usando o NFNUM mesmo, não chegamos a nos preocupar com isso devido ser um volume baixo de NFS, talvez um chamado no componente XX-CSC-BR-NFE lhe ajude.
Abraço,
Bruno Lima

NFS-e Salvador - BA

Olá,
Alguém já desenvolveu a comunicação para a Nota Fiscal Eletronica de Serviso para Salvador, trabalhamos com outros municipios onde geramos um txt e informamos no site, porém até onde vi no caso de Salvador precisamos de uma comunicação via Web Service para enviar um xml.
Alguém sabe me indicar uma solução?

Oi Rodrigo
O problema é que a documentação da prefeitura de Salvador não é clara quanto aos requisitos; assim como muitas outras prefeituras que "seguem" o padrão ABRASF. O padrão foi definido mas de fato as prefeituras adotam o que lhe convêm do padrão!
No caso, a prefeitura de Salvador exige que tanto a RPS quanto o lote sejam assinados. Neste caso seguem o que diz o manual da ABRASF.
2.2.5 Uso de Assinatura com Certificado Digital
Para garantir a autenticidade dos dados gerados, algumas informações
deverão ser assinadas digitalmente. Abaixo segue as informações que deverão
ser assinadas e quem deverá fazê-lo em cada momento:
• O RPS, pelo contribuinte, antes do envio do mesmo através do Lote de RPS;
• O Lote de RPS, pelo contribuinte, antes do envio do mesmo;
• A NFS-e:
o Pela prefeitura e pelo contribuinte, quando gerada pela Aplicação On Line;
o Pela prefeitura nos demais casos;
• O Pedido de cancelamento da NFS-e, pelo contribuinte;
• A Confirmação de cancelamento da NFS-e, pela prefeitura;
Dê uma olhada na thread abaixo:
http://scn.sap.com/thread/3468237
Pedro Baroni... se puder ajudar!
Abraço
Eduardo Chagas

NFS-e município de São Paulo

Olá.
Alguém saberia me dizer se a solução standard da SAP para Nota Fiscal Eletrônica de Serviços do município de São Paulo se resume a nota "SAP Note 981687 - NFe: For Services in Muncipio Sao Paulo"?
Pergunto porque esta nota apenas gera um arquivo TXT que deve ser enviado manualmente para a prefeitura.
Como hoje a prefeitura de São Paulo já disponibiliza Web Services para comunicação direta com os sistemas dos contribuintes, gostaria de saber se a SAP tem alguma solução mais atualizada.
Abraços e Obrigado!

Bom dia André,
Atualmente sim o report é a única solução.. Está em discussão entre os municípios de adotar um padrão único (SP ainda não está neste padrão) para emissão online de NFS-e. A SAP não tem pretensão de desenvolver a solução caso os municípios não cheguem a um acordo.
Atenciosamente, Fernando Da Ró

NFS-e - Nota Fiscal Eletrônica de Serviço

O município de Rio Verde-GO está realizando a implementação de nota fiscal eletrônica de serviços, a SAP tem algum produto específico voltado para tal?
Ou existe alguma sugestão de implementação?
Temos uma filial nesta cidade e teremos de implementar a NFS-e até maio deste ano.
Aguardo retorno.
Obrigado,
Mateus.

MATEUS PARREIRA GUIMARÃES wrote:
> Outra informação, você sabe me falar qual produto da SAP é específico para este cenário?
Nao entendi sua pergunta, eu havia acabado de dizer que não há produto standard SAP para NFS-e. :P
Conforme falei, o que vc pode fazer é utilizar a mesma arquitetura do GRC (desenvolvimentos ABAP e interfaces via SAP PI) para a integração com as prefeituras. Já existem alguns clientes live com solucões nesse formato, desenvolvidas por algumas consultorias.
Abs,
Henrique.

NFS-e Município de Salvador-BA (Certificado IMBUI)

Pessoal,
Temos atualmente uma customização da solução de NF-e para NFS-e Município de Salvador-BA.
Recentemente eles fizeram um ajuste no sistema deles, pois pelo que eles falaram antigamente não havia validação alguma, mensagem, assinatura, etc.
A arquitetura do sistema atual deles diferem entre Produção e Homologação, sendo que em homologação além do certificado de NFe, que a solução da SEFAZ usa, eles pedem mais um certificado para realizar a comunicação HTTPS.
Tentei regerar o certificado da SEFAZ com a esperança de que esse cetificado adicional fosse para a cadeia de certificação, mas não obtive sucesso.
Também no SAP PI não encontrei como utilizar esses dois certificados ao mesmo tempo no Receiver SOAP Adapter.
O certificado adicional se encontra ao final do link abaixo disponível para download:
https://notahml.salvador.ba.gov.br/rps/
Alguém já fez esse trabalho de comunicar com a solução de NFS-e do Município de Salvador-BA. Ou poderia me dar uma luz de como consigo utilizar esses dois certificados ao mesmo tempo para essa comunicação?

Oi Rodrigo
O problema é que a documentação da prefeitura de Salvador não é clara quanto aos requisitos; assim como muitas outras prefeituras que "seguem" o padrão ABRASF. O padrão foi definido mas de fato as prefeituras adotam o que lhe convêm do padrão!
No caso, a prefeitura de Salvador exige que tanto a RPS quanto o lote sejam assinados. Neste caso seguem o que diz o manual da ABRASF.
2.2.5 Uso de Assinatura com Certificado Digital
Para garantir a autenticidade dos dados gerados, algumas informações
deverão ser assinadas digitalmente. Abaixo segue as informações que deverão
ser assinadas e quem deverá fazê-lo em cada momento:
• O RPS, pelo contribuinte, antes do envio do mesmo através do Lote de RPS;
• O Lote de RPS, pelo contribuinte, antes do envio do mesmo;
• A NFS-e:
o Pela prefeitura e pelo contribuinte, quando gerada pela Aplicação On Line;
o Pela prefeitura nos demais casos;
• O Pedido de cancelamento da NFS-e, pelo contribuinte;
• A Confirmação de cancelamento da NFS-e, pela prefeitura;
Dê uma olhada na thread abaixo:
http://scn.sap.com/thread/3468237
Pedro Baroni... se puder ajudar!
Abraço
Eduardo Chagas

RMAN, RAC, NFS, and server lock ups

Good day. My environment is:
--a 2-node RAC
--Enterprise Edition 11.2.0.3
--RHEL 5.1
The goal is to use RMAN to push backups to a shared NFS mount (on a different server). Both nodes will have access to this location (in the event one node goes down, the other can still run backups). Easy, right?
Wrong.
I've tried every NFS mount option in the book. Most work just fine, some don't. When I use the recommended NFS mount options:
rw,bg,hard,nointr,rsize=32768,wsize=32768,tcp, vers=3,timeo=600, actimeo=0
or
rw,bg,hard,nointr,rsize=32768,wsize=32768,proto=tcp,noac,forcedirectio, vers=3,suid
The mount works normally. I can "ls" and "mkdir" and "touch" and "vi" and "cp" files back and forth from the NFS backup location to the RAC node all day long. No problems. However, when I try to do almost anything in RMAN which requires writing to the NFS backup location such as the command "backup archive all delete input;" (or even things as simple as a Crosscheck or RMAN configuration change which writes any changes back to the autobackup ControlFile) the node locks up. There are no errors (or if there are, I don't know where to find them), even when I use RMAN log.
Just to recap: I run a Crosscheck (or any RMAN process that writes to the NFS backup location), the node will lock up, and I can let it sit for a day, inaccessible, with CRSCTL on the other node saying it's offline, and the node will never come out of a "frozen" state. It cannot be pinged or connected to.
I think I can safely rule out NFS mount options at this point.
I understand (after extensive reading of MOS docs and testing) that RAC RMAN can and does suffer from inefficient I/O when writing to an NFS mount. I don't think that's the culprit either. The autobackup ControlFile is not that big and I cannot see how running a simple Crosscheck would lock an entire node.
I am hoping someone has encountered this in the past and hopefully it's just a simple misconfiguration somewhere.

My NFS line in /etc/fstab is (these options are for supporting 11.2.0.3, 11.1.0.7, and 10.2.0.4/5 simultaneously): server.domain:/NFS_Export /backup nfs rw,bg,hard,nointr,rsize=32768,wsize=32768,tcp,actimeo=0,vers=3,timeo=600 0 0
Before you installed GI, did you by chance do a yum update? I've encountered a similar issue which ended up being due to mkinitrd creating a corrupted kernel; mkinitrd is invoked during the GI installation when the ADVM drivers are added and in my case mkinitrd created a new kernel prior to the new kernel being installed. Second to that, make sure you have the matching kernel headers to your kernel version. If they are different then you could probably get away with just creating a new kernel with mkinitrd and relinking GI/RDBMS homes, but be prepared to wipe GI and reinstall.

NFS causes whole system hang

I have a home server that I just set up recently that runs Arch linux. It exports a couple of external hard drives via NFS. I have been mouting them with autofs on my laptop. However, after several hours the entire system completely hangs up. I originally thought it had something to do with the rpc-gssd daemon that the NFS wiki page recommends running as it was dying in a strange way and I thought that may have been related to the hang ups. After implementing a different workaround (blacklist rpcsec_gss_krb5) and disabling rpc-gssd, I am still having the same hang issue.
Here is what happens:
I boot up my computer, start Firefox, Thunderbird, various terminals, etc. I mount the NFS share with autofs by opening up the /media/net/atomic/qx2_data directory. After a while, the NFS mounts in Thunar start disappering momentarily. Then a little while later the system completely hangs and requires a hard reboot. The end of the log from journalctl is posted below.
Right now I have disabled autofs and I will only mount the drives on the server via SFTP to avoid this problem, but I would really like to get this debugged. Also, this is not likely related to any sort of a connection issue as both computers are hardwired to the same Gigabit Ethernet switch.
Any ideas on what might be going on here?
/etc/autofs/auto.net:
atomic -fstype=nfs4,rw,async,sec=sys,bg,intr atomic.local:/
Log:
Dec 17 16:33:35 watatsumi automount[19747]: key ".hidden" not found in map source(s).
Dec 17 16:34:51 watatsumi automount[19747]: key ".hidden" not found in map source(s).
Dec 17 16:36:07 watatsumi automount[19747]: key ".hidden" not found in map source(s).
Dec 17 16:37:23 watatsumi automount[19747]: key ".hidden" not found in map source(s).
Dec 17 16:38:35 watatsumi automount[19747]: key ".hidden" not found in map source(s).
Dec 17 16:39:51 watatsumi automount[19747]: key ".hidden" not found in map source(s).
Dec 17 16:41:07 watatsumi automount[19747]: key ".hidden" not found in map source(s).
Dec 17 16:42:23 watatsumi automount[19747]: key ".hidden" not found in map source(s).
Dec 17 16:43:39 watatsumi automount[19747]: key ".hidden" not found in map source(s).
Dec 17 16:45:16 watatsumi kernel: BUG: soft lockup - CPU#5 stuck for 23s! [htop:2505]
Dec 17 16:45:16 watatsumi kernel: Modules linked in: usbtmc auth_rpcgss oid_registry nfsv4 tun joydev snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd fuse nvidia(PO) iTCO_wdt iTCO_vendor_support uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core snd_usb_audio videodev snd_usbmidi_lib snd_rawmidi media snd_seq_device arc4 evdev microcode psmouse serio_raw iwldvm mac80211 snd_hda_codec_realtek iwlwifi snd_hda_intel snd_hda_codec cfg80211 snd_hwdep drm snd_pcm jme jmb38x_ms rfkill mii snd_page_alloc memstick snd_timer i2c_i801 mei_me snd i2c_core soundcore mei thermal shpchp wmi lpc_ich processor battery ac button video pcspkr nfs lockd
Dec 17 16:45:16 watatsumi kernel: sunrpc fscache ext4 crc16 mbcache jbd2 sd_mod hid_generic usbhid hid ahci libahci libata ehci_pci firewire_ohci sdhci_pci xhci_hcd scsi_mod ehci_hcd sdhci firewire_core crc_itu_t mmc_core usbcore usb_common
Dec 17 16:45:16 watatsumi kernel: CPU: 5 PID: 2505 Comm: htop Tainted: P O 3.12.5-1-ARCH #1
Dec 17 16:45:16 watatsumi kernel: Hardware name: CLEVO P150HMx/P150HMx, BIOS 4.6.4 08/09/2011
Dec 17 16:45:16 watatsumi kernel: task: ffff880801678000 ti: ffff8807dcbec000 task.ti: ffff8807dcbec000
Dec 17 16:45:16 watatsumi kernel: RIP: 0010:[<ffffffff814f4f8e>] [<ffffffff814f4f8e>] _raw_spin_lock+0x2e/0x40
Dec 17 16:45:16 watatsumi kernel: RSP: 0018:ffff8807dcbedd88 EFLAGS: 00000297
Dec 17 16:45:16 watatsumi kernel: RAX: 0000000000000082 RBX: ffffffff81299133 RCX: 0000000000000000
Dec 17 16:45:16 watatsumi kernel: RDX: 0000000000000083 RSI: ffffffff8172447b RDI: ffffffff818063c0
Dec 17 16:45:16 watatsumi kernel: RBP: ffff8807dcbedd88 R08: 0000000000017b80 R09: ffff88080e83ce00
Dec 17 16:45:16 watatsumi kernel: R10: ffff8807dcbedfd8 R11: ffffffff81209fbd R12: ffff8807dcbedea0
Dec 17 16:45:16 watatsumi kernel: R13: ffff8807dcbede93 R14: ffffffff812981f2 R15: ffff8807dcbedcf8
Dec 17 16:45:16 watatsumi kernel: FS: 00007f52ddf3c700(0000) GS:ffff88082f540000(0000) knlGS:0000000000000000
Dec 17 16:45:16 watatsumi kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Dec 17 16:45:16 watatsumi kernel: CR2: 00007f52ddf7d000 CR3: 00000007cb1d2000 CR4: 00000000000407e0
Dec 17 16:45:16 watatsumi kernel: Stack:
Dec 17 16:45:16 watatsumi kernel: ffff8807dcbedda0 ffffffff811bdee9 ffff88077db89c18 ffff8807dcbeddb8
Dec 17 16:45:16 watatsumi kernel: ffffffff811c0089 ffff88064dd7d9c0 ffff8807dcbedde8 ffffffff8120d9db
Dec 17 16:45:16 watatsumi kernel: ffff88064dd7d9c0 0000000000000005 ffff8807ba6dc480 ffffffff8120df90
Dec 17 16:45:16 watatsumi kernel: Call Trace:
Dec 17 16:45:16 watatsumi kernel: [<ffffffff811bdee9>] inode_sb_list_add+0x19/0x60
Dec 17 16:45:16 watatsumi kernel: [<ffffffff811c0089>] new_inode+0x29/0x30
Dec 17 16:45:16 watatsumi kernel: [<ffffffff8120d9db>] proc_pid_make_inode+0x1b/0x100
Dec 17 16:45:16 watatsumi kernel: [<ffffffff8120df90>] ? proc_map_files_lookup+0x160/0x160
Dec 17 16:45:16 watatsumi kernel: [<ffffffff8120dfab>] proc_task_instantiate+0x1b/0xc0
Dec 17 16:45:16 watatsumi kernel: [<ffffffff8120e28f>] proc_fill_cache+0xbf/0xe0
Dec 17 16:45:16 watatsumi kernel: [<ffffffff8120ea1d>] proc_task_readdir+0x18d/0x3b0
Dec 17 16:45:16 watatsumi kernel: [<ffffffff811b75ad>] iterate_dir+0xad/0xe0
Dec 17 16:45:16 watatsumi kernel: [<ffffffff811b79e2>] SyS_getdents+0x92/0x120
Dec 17 16:45:16 watatsumi kernel: [<ffffffff811b76c0>] ? fillonedir+0xe0/0xe0
Dec 17 16:45:16 watatsumi kernel: [<ffffffff814fcfed>] system_call_fastpath+0x1a/0x1f
Dec 17 16:45:16 watatsumi kernel: Code: 66 90 55 65 48 8b 04 25 70 c7 00 00 48 89 e5 83 80 44 e0 ff ff 01 b8 00 01 00 00 f0 66 0f c1 07 0f b6 d4 38 c2 75 04 5d c3 f3 90 <0f> b6 07 38 d0 75 f7 5d c3 66 0f 1f 84 00 00 00 00 00 66 66 66
Dec 17 16:45:16 watatsumi kernel: BUG: soft lockup - CPU#6 stuck for 23s! [umount.nfs4:30556]
Dec 17 16:45:16 watatsumi kernel: Modules linked in: usbtmc auth_rpcgss oid_registry nfsv4 tun joydev snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd fuse nvidia(PO) iTCO_wdt iTCO_vendor_support uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core snd_usb_audio videodev snd_usbmidi_lib snd_rawmidi media snd_seq_device arc4 evdev microcode psmouse serio_raw iwldvm mac80211 snd_hda_codec_realtek iwlwifi snd_hda_intel snd_hda_codec cfg80211 snd_hwdep drm snd_pcm jme jmb38x_ms rfkill mii snd_page_alloc memstick snd_timer i2c_i801 mei_me snd i2c_core soundcore mei thermal shpchp wmi lpc_ich processor battery ac button video pcspkr nfs lockd
Dec 17 16:45:16 watatsumi kernel: sunrpc fscache ext4 crc16 mbcache jbd2 sd_mod hid_generic usbhid hid ahci libahci libata ehci_pci firewire_ohci sdhci_pci xhci_hcd scsi_mod ehci_hcd sdhci firewire_core crc_itu_t mmc_core usbcore usb_common
Dec 17 16:45:16 watatsumi kernel: CPU: 6 PID: 30556 Comm: umount.nfs4 Tainted: P O 3.12.5-1-ARCH #1
Dec 17 16:45:16 watatsumi kernel: Hardware name: CLEVO P150HMx/P150HMx, BIOS 4.6.4 08/09/2011
Dec 17 16:45:16 watatsumi kernel: task: ffff8807c902e840 ti: ffff88064fe5c000 task.ti: ffff88064fe5c000
Dec 17 16:45:16 watatsumi kernel: RIP: 0010:[<ffffffff814f4f83>] [<ffffffff814f4f83>] _raw_spin_lock+0x23/0x40
Dec 17 16:45:16 watatsumi kernel: RSP: 0018:ffff88064fe5ddb0 EFLAGS: 00000202
Dec 17 16:45:16 watatsumi kernel: RAX: 0000000000002c2c RBX: f97a1072bc3dd003 RCX: ffffffff818c01e0
Dec 17 16:45:16 watatsumi kernel: RDX: 000000000000002b RSI: 0000000000000001 RDI: ffff880667e6d438
Dec 17 16:45:16 watatsumi kernel: RBP: ffff88064fe5ddb0 R08: 0000000000000000 R09: 0667f127400c0000
Dec 17 16:45:16 watatsumi kernel: R10: f97a1072bc3dd003 R11: 0000000000000001 R12: ffff88064fe5dd30
Dec 17 16:45:16 watatsumi kernel: R13: ffff88064fe5ddb0 R14: ffff880667f12730 R15: ffff880667f126a8
Dec 17 16:45:16 watatsumi kernel: FS: 00007fdbfd3b3780(0000) GS:ffff88082f580000(0000) knlGS:0000000000000000
Dec 17 16:45:16 watatsumi kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Dec 17 16:45:16 watatsumi kernel: CR2: 00007f63631ff000 CR3: 00000006a0de3000 CR4: 00000000000407e0
Dec 17 16:45:16 watatsumi kernel: Stack:
Dec 17 16:45:16 watatsumi kernel: ffff88064fe5ddf8 ffffffff811e612c ffff880667f12730 0000000000000000
Dec 17 16:45:16 watatsumi kernel: ffff8807d797e000 ffff8807d797e0a0 ffffffffa143fe40 ffff880099c279c0
Dec 17 16:45:16 watatsumi kernel: ffff880674e30620 ffff88064fe5de20 ffffffff811a6a60 0000000000000025
Dec 17 16:45:16 watatsumi kernel: Call Trace:
Dec 17 16:45:16 watatsumi kernel: [<ffffffff811e612c>] fsnotify_unmount_inodes+0x11c/0x1b0
Dec 17 16:45:16 watatsumi kernel: [<ffffffff811a6a60>] generic_shutdown_super+0x40/0xf0
Dec 17 16:45:16 watatsumi kernel: [<ffffffff811a6cd2>] kill_anon_super+0x12/0x20
Dec 17 16:45:16 watatsumi kernel: [<ffffffffa03eb18b>] nfs_kill_super+0x1b/0x30 [nfs]
Dec 17 16:45:16 watatsumi kernel: [<ffffffff811a70bd>] deactivate_locked_super+0x3d/0x60
Dec 17 16:45:16 watatsumi kernel: [<ffffffff811a76a6>] deactivate_super+0x46/0x60
Dec 17 16:45:16 watatsumi kernel: [<ffffffff811c350f>] mntput_no_expire+0xef/0x150
Dec 17 16:45:16 watatsumi kernel: [<ffffffff811c3596>] mntput+0x26/0x40
Dec 17 16:45:16 watatsumi kernel: [<ffffffff811c36ad>] namespace_unlock+0xfd/0x110
Dec 17 16:45:16 watatsumi kernel: [<ffffffff811c4803>] SyS_umount+0x1c3/0x3a0
Dec 17 16:45:16 watatsumi kernel: [<ffffffff814fcfed>] system_call_fastpath+0x1a/0x1f
Dec 17 16:45:16 watatsumi kernel: Code: 05 e8 52 84 da ff 5d c3 66 66 66 66 90 55 65 48 8b 04 25 70 c7 00 00 48 89 e5 83 80 44 e0 ff ff 01 b8 00 01 00 00 f0 66 0f c1 07 <0f> b6 d4 38 c2 75 04 5d c3 f3 90 0f b6 07 38 d0 75 f7 5d c3 66
Dec 17 16:45:16 watatsumi kernel: BUG: soft lockup - CPU#7 stuck for 23s! [ifconfig:30557]
Last edited by alex.forencich (2013-12-18 02:02:58)

Hi Alex - autofs mounts on demand/request, and unmounts a filesystem after 10 minutes of non-use by default. If you set the timeout to zero (auto.master), it disables this timeout. If this is an NFSv4 umount bug, then I don't think this will help you as you'll have to umount at some stage (e.g. shutting down).

NFS Commnication channel errors for deleting and placing

Hi All,
I was trying File to file scenario.
I am picking the file from App server(AL11) using NFS Adapter and the processing Mode is Delete
In comm channel monitor it showing an error as
Sender channel error:
Error: File '/staging/INTERFACE/SAP/ca/kar370.txt' - deleting after processing failed
Same way while placing the file
Receiver channel error:
Error: Message processing failed: FileNotFoundException: /staging/INTERFACE/SAP/ca/test120110906-122051-980.txt (Permission denied)
Whether i dont have the permission to delete and place the file from and to the App server(AL11)?
What is the procedure in order to make it possible.
Thanks
Sai

Hi All,
Thanks to every one.
The problem is solved ,
Basis Guy has given the permissions, and i am able to place and delete the files .
Thanks
Sai

Changing homedirectories from AFP to NFS cures all Office Problems?

Hi all,
well a lot of us do have a lot of problmes using Microsoft Office. New files can't be copied to the server (with unknown error -50), saving files fail because of wired netwrok errors or full disks, duplicating files cause complete file loss (the copy and the oridignal file itself), wordfiles seem to be locked (should i make a copy?) trying to open them, over and over there are Word Work Files and uncountable nummers auf Autorecovery files with zero bytes, Word bothering you to many files are open (with not a single file opend) ...
Well this all seems to be a problem of office combined with homedirectory shared through AFP. A Friend of mine told me, that he has no problems with office. The only difference betwenn his infrastructure and mine is, that he uses NFS for sharing homedirectories.
So i did the Following:
I created a new sharepoint for homedirectories and shared it through NFS. Created a new user, using this sharepoint for his homedirectory. Then i worked with the NFS-User on an AFP-sharepoint (like creating a Word file, doing changes and saving it). Then i worked on the same document with an user thats homedirectory is shared through AFP. Everytime i did a change to the document and saved it, a new Word Work File was created next to the original file. After several iterations with the AFP-user there error that the document is allready opend came up...
So my first findings comparing NFS users with AFP users is, that the problems using Office are completely gone when using NFS for homedirectories.
Now the questions for me are:
1.) is anybody there that can approve my findings?
2.) are there any reasons not to use NFS for homedirectories?
3.) which protocol do you use for sharing homedirectories?
4.) what would be the smartest way to change / move APF shared homedirecties to NFS?
I allready did the following to change an AFP shared homedirectory to NFS:
- Set the users home dir from /Users/ to none (in Workgroup Manager)
- as root via terminal mv /Users/myuser /NFSUsers/
- in Workgroupmanager set the useres homedir from none to /NFSUsers/
This worked well (for a short look on it). The only problem was, that the subfolders in the sidebar of the Finder window did not work, and had to be reseted.
Any other suggestions?
Greetings
MacSEK

Hello,
Today a friend reported this problem to me. This problem was only to Word, to Excel no.
In my case the guilty was the add-in PDFCOMPLETE in WORD 2013.
I saw it in programs list on Control Panel. It belong to PDF Complete, Inc.
They have a HP computer. When I uninstalled this add-in from programs list the problem solved !
I did that today. Now they are able to change language and also to put tone on Greek vowels.
When I uninstalled the PDFCOMPLETE I saw on uninstallation window the HP icon !
It seems a file related with HP programs created the problem.

ORA-27086: unable to lock file over NFS -- but it's NOT Netapp!

My 10.2 database crashed, and when it came back I got the following error:
ORA-00202: control file: '/local/opt/oracle/product/10.2.0/dbs/lkFOOBAR'
ORA-27086: unable to lock file - already in use
Linux-x86_64 Error: 11: Resource temporarily unavailable
This is a classic symptom of a Netapp problem, which likes to hold file locks open on NFS mounts. There is a standard procedure for clearing those locks; see, for instance, document 429912.1 on Metalink.
Unfortunately, my files are mounted on an Isilon, one of Netapp's twisted cousins. I can find no references to "isilon" on Metalink, and we are at a loss how to resolve this.
My sysadmin assures me that "there are no locks on the Isilon". But I know this cannot be the case, because if I do the following:
1. delete the lockfile /local/opt/oracle/product/10.2.0/dbs/lkFOOBAR, and then
2. move my controlfiles aside, and then copy them back into place,
then the database will mount. However, it will not open, because now all the datafiles have locks.
Is there anyone with experience in clearing NFS locks? I know this is more of a SA task than DBA, but I am sure my SA has overlooked something.
Thanks

New information:
As stated above, I moved the controlfiles aside and then copied them back into place, like this:
mv control01.ctl control01-bak.ctl
cp control01-bak.ctl control01.ctlDid that for each controlfile, and then the database mounted.
But, after rebooting the machine, we discovered that all locks were back in place-- it looks like the system is locking the files on boot-up, and not letting them go. The lock is held by PID 1, which is init.
sculkget: lock held by PID: 1This is definitely looking like a major system issue, and not a DBA issue, and hence I have little right to expect assistance in this forum. But nonetheless I lay my situation out here before you all in case someone else recognizes my problem before the server bursts into flames!
The system is CentOS 4.5-- not my choice, but that's the way it is.

NFS-e

Similar Messages

Maybe you are looking for