Servers in cluster go down : twice with different reasons

Hi All,
 Our environment is deployed as a cluster with two servers. The configuration being
 WL server 5.1 with SP8 on Solaris. Everything was dandy until the cluster went down
 twice in a period of 5 days each time with a different reason. Any help in this regard
 is highly appreciated.
 Thanks-
 vijay
 First fall :
 The first server in the cluster went down after spitting out the "listen failed"
 message a couple of thousand times. Immediately following it the second server shut
 down with the same error. I understand that in answer to a similar posting in the
 group it was suggested to increase the file descriptor count to 1024 or all the way
 upto 4096, but doing so would it solve the problem in total.
 Fri Jul 05 09:38:31 GMT 2002:<E> <ListenThread> Listen failed, failure count:
 '2148'
 java.net.SocketException: Too many open files
 at java.net.PlainSocketImpl.socketAccept(Native Method)
 at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:421)
 at java.net.ServerSocket.implAccept(ServerSocket.java:243)
 at java.net.ServerSocket.accept(ServerSocket.java:222)
 at weblogic.t3.srvr.ListenThread.run(ListenThread.java:277)
 Fri Jul 05 09:38:31 GMT 2002:<A> <ListenThread> ListenThread.run() failed:
 java.lang.IllegalArgumentException: timeout value is negative
 at java.lang.Thread.sleep(Native Method)
 at weblogic.t3.srvr.ListenThread.run(ListenThread.java:307)
 Fall two:
 This time around the first server had the following exception when looking up the
 JNDI for a JMS queue specifically but preceeding with the following exception. And
 following it the second server timed with the same exception.
 Mon Jul 08 16:41:18 GMT 2002: <WebAppServletContext-SmartChain> MovementControllerServlet:
 init
 Mon Jul 08 17:59:14 GMT 2002:<E> <HttpSessionContext> Unexpected error in HTTP session
 timeout callback
 weblogic.cluster.replication.NotFoundException: unregister unable to find object
 1549818748307493344
 at weblogic.cluster.replication.ReplicationManager.find(ReplicationManager.java:596)
 at weblogic.cluster.replication.ReplicationManager.unregister(ReplicationManager.java:644)
 at weblogic.servlet.internal.session.ReplicatedSession.invalidate(ReplicatedSession.java:259)
 at weblogic.servlet.internal.session.ReplicatedSessionContext.invalidateSession(ReplicatedSessionContext.java:131)
 at weblogic.servlet.internal.session.SessionContext$SessionInvalidator.invalidateSessions(SessionContext.java:502)
 at weblogic.servlet.internal.session.SessionContext$SessionInvalidator.trigger(SessionContext.java:479)
 at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:197)
 at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:191)
 at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:60)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
 --------------- nested within: ------------------
 weblogic.utils.NestedError: Can't unregister an ROID that does not exist - with nested
 exception:
 [weblogic.cluster.replication.NotFoundException: unregister unable to find object
 1549818748307493344]
 at weblogic.servlet.internal.session.ReplicatedSession.invalidate(ReplicatedSession.java:267)
 at weblogic.servlet.internal.session.ReplicatedSessionContext.invalidateSession(ReplicatedSessionContext.java:131)
 at weblogic.servlet.internal.session.SessionContext$SessionInvalidator.invalidateSessions(SessionContext.java:502)
 at weblogic.servlet.internal.session.SessionContext$SessionInvalidator.trigger(SessionContext.java:479)
 at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:197)
 at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:191)
 at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:60)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
 Mon Jul 08 18:03:28 GMT 2002: <Cluster> Timed out server
 Mon Jul 08 18:03:28 GMT 2002: <ConflictHandler> ConflictStop smartchain.SecurityFactory:com.smartchain.datacenter.eam.SecurityFactoryImpl
 (from [email protected]:[7001,7001,7002,7002,7001,-1])
 Mon Jul 08 18:03:28 GMT 2002: <ConflictHandler> ConflictStop smartchain.LoginManager:com.smartchain.datacenter.eam.LoginManagerImpl
 (from [email protected]:[7001,7001,7002,7002,7001,-1])
 Mon Jul 08 18:03:49 GMT 2002: <RJVM> Signaling peer -2914132898719179429S10.7.68.69:[7001,7001,7002,7002,7001,-1]
 gone: weblogic.rjvm.PeerGoneException:
 - with nested exception:
 [java.io.EOFException]
 javax.naming.NameNotFoundException: 'javax.jms.SEDEM'; remaining name 'SEDEM'
 at weblogic.jndi.toolkit.BasicWLContext.resolveName(BasicWLContext.java:745)
 at weblogic.jndi.toolkit.BasicWLContext.lookup(BasicWLContext.java:133)
 at weblogic.jndi.toolkit.BasicWLContext.lookup(BasicWLContext.java:574)
 at javax.naming.InitialContext.lookup(InitialContext.java:350)
 at com.smartchain.datacenter.sedem.servlet.BLEventsHandleServlet.dispatch(BLEventsHandleServlet.java:240)
 at com.smartchain.datacenter.sedem.servlet.BLEventsHandleServlet.service(BLEventsHandleServlet.java:176)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
 at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
 at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
 at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
 at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
 at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)

Hi All
 I'm also having similar problem with them. The server went a few times with the
 similar error.
 We are using WL 5.1 SP12 with file descriptor set to 4096 in Solaris.
 I'm very desperate to find a solution to this.
 Thanks in advance.
 Herman Wijaya
 Rajesh Mirchandani <[email protected]> wrote:
 >You should try increasing the FDs to 4096 and see if the same problem
 >can be reproduced.
 >
 >Kumar Allamraju wrote:
 >
 >> vijay singh wrote:
 >>
 >> > Hi All,
 >> >
 >> > Our environment is deployed as a cluster with two servers. The
 >configuration being
 >> > WL server 5.1 with SP8 on Solaris. Everything was dandy until the
 >cluster went down
 >> > twice in a period of 5 days each time with a different reason. Any
 >help in this regard
 >> > is highly appreciated.
 >> >
 >> > Thanks-
 >> >
 >> > vijay
 >> >
 >> > First fall :
 >> > ------------
 >> >
 >> > The first server in the cluster went down after spitting out the
 >"listen failed"
 >> > message a couple of thousand times. Immediately following it the
 >second server shut
 >> > down with the same error. I understand that in answer to a similar
 >posting in the
 >> > group it was suggested to increase the file descriptor count to 1024
 >or all the way
 >> > upto 4096, but doing so would it solve the problem in total.
 >> >
 >> > Fri Jul 05 09:38:31 GMT 2002:<E> <ListenThread> Listen failed,
 >failure count:
 >> > '2148'
 >> > java.net.SocketException: Too many open files
 >> > at java.net.PlainSocketImpl.socketAccept(Native Method)
 >> > at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:421)
 >> > at java.net.ServerSocket.implAccept(ServerSocket.java:243)
 >> > at java.net.ServerSocket.accept(ServerSocket.java:222)
 >> > at weblogic.t3.srvr.ListenThread.run(ListenThread.java:277)
 >>
 >> This is indeed a fairly harmless failure. Whenever a
 >> ServerSocket.accept() fails, we increment a count and wait for a period
 >> of time (starting with 10secs) that increases on successive failures.
 >> Although, the failures are harmless, they need to be monitored - if
 >> there are too many of them, it is indicative of something that is not
 >> quite right with the network [or in the tuning of the native OS for
 >TCP].
 >>
 >> You also might want to monitor netstat output and see how long the
 >> sockets are being kept in CLOSE_WAIT state. Sometimes tuning one of
 >> those TCP/IP parameters might help.
 >>
 >> >
 >> > Fri Jul 05 09:38:31 GMT 2002:<A> <ListenThread> ListenThread.run()
 >failed:
 >> > java.lang.IllegalArgumentException: timeout value is negative
 >> > at java.lang.Thread.sleep(Native Method)
 >> > at weblogic.t3.srvr.ListenThread.run(ListenThread.java:307)
 >> >
 >>
 >> I guess this might have been fixed in one of the latest SP's of 51.
 >> I would suggest that you try with latest SP (SP12) and let us know
 >if
 >> you still this problem.
 >>
 >> > Fall two:
 >> > ---------
 >> >
 >> > This time around the first server had the following exception when
 >looking up the
 >> > JNDI for a JMS queue specifically but preceeding with the following
 >exception. And
 >> > following it the second server timed with the same exception.
 >> >
 >> > Mon Jul 08 16:41:18 GMT 2002: <WebAppServletContext-SmartChain>
 >MovementControllerServlet:
 >> > init
 >> > Mon Jul 08 17:59:14 GMT 2002:<E> <HttpSessionContext> Unexpected
 >error in HTTP session
 >> > timeout callback
 >> > weblogic.cluster.replication.NotFoundException: unregister unable
 >to find object
 >> > 1549818748307493344
 >> > at weblogic.cluster.replication.ReplicationManager.find(ReplicationManager.java:596)
 >> > at weblogic.cluster.replication.ReplicationManager.unregister(ReplicationManager.java:644)
 >> > at weblogic.servlet.internal.session.ReplicatedSession.invalidate(ReplicatedSession.java:259)
 >> > at weblogic.servlet.internal.session.ReplicatedSessionContext.invalidateSession(ReplicatedSessionContext.java:131)
 >> > at weblogic.servlet.internal.session.SessionContext$SessionInvalidator.invalidateSessions(SessionContext.java:502)
 >> > at weblogic.servlet.internal.session.SessionContext$SessionInvalidator.trigger(SessionContext.java:479)
 >> > at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:197)
 >> > at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:191)
 >> > at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:60)
 >> > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
 >> > --------------- nested within: ------------------
 >> > weblogic.utils.NestedError: Can't unregister an ROID that does not
 >exist - with nested
 >> > exception:
 >> > [weblogic.cluster.replication.NotFoundException: unregister unable
 >to find object
 >> > 1549818748307493344]
 >> > at weblogic.servlet.internal.session.ReplicatedSession.invalidate(ReplicatedSession.java:267)
 >> > at weblogic.servlet.internal.session.ReplicatedSessionContext.invalidateSession(ReplicatedSessionContext.java:131)
 >> > at weblogic.servlet.internal.session.SessionContext$SessionInvalidator.invalidateSessions(SessionContext.java:502)
 >> > at weblogic.servlet.internal.session.SessionContext$SessionInvalidator.trigger(SessionContext.java:479)
 >> > at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:197)
 >> > at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:191)
 >> > at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:60)
 >> > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
 >> >
 >> > Mon Jul 08 18:03:28 GMT 2002: <Cluster> Timed out server
 >> > Mon Jul 08 18:03:28 GMT 2002: <ConflictHandler> ConflictStop smartchain.SecurityFactory:com.smartchain.datacenter.eam.SecurityFactoryImpl
 >> > (from [email protected]:[7001,7001,7002,7002,7001,-1])
 >> > Mon Jul 08 18:03:28 GMT 2002: <ConflictHandler> ConflictStop smartchain.LoginManager:com.smartchain.datacenter.eam.LoginManagerImpl
 >> > (from [email protected]:[7001,7001,7002,7002,7001,-1])
 >> > Mon Jul 08 18:03:49 GMT 2002: <RJVM> Signaling peer -2914132898719179429S10.7.68.69:[7001,7001,7002,7002,7001,-1]
 >> > gone: weblogic.rjvm.PeerGoneException:
 >> > - with nested exception:
 >> > [java.io.EOFException]
 >> > javax.naming.NameNotFoundException: 'javax.jms.SEDEM'; remaining
 >name 'SEDEM'
 >> > at weblogic.jndi.toolkit.BasicWLContext.resolveName(BasicWLContext.java:745)
 >> > at weblogic.jndi.toolkit.BasicWLContext.lookup(BasicWLContext.java:133)
 >> > at weblogic.jndi.toolkit.BasicWLContext.lookup(BasicWLContext.java:574)
 >> > at javax.naming.InitialContext.lookup(InitialContext.java:350)
 >> > at com.smartchain.datacenter.sedem.servlet.BLEventsHandleServlet.dispatch(BLEventsHandleServlet.java:240)
 >> > at com.smartchain.datacenter.sedem.servlet.BLEventsHandleServlet.service(BLEventsHandleServlet.java:176)
 >> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
 >> > at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
 >> > at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
 >> > at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
 >> > at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
 >> > at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
 >> > at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
 >> > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
 >> >
 >>
 >> See the above message "Timed out server" which is not a good sign.
 >> Either GC is running for more than 30 secs or this server is not
 >> receiving heartbeats from the other servers causing the other server
 >be
 >> dropping out of the cluster view. You may want to enable verbosegc
 >and
 >> monitor the heap usage and GC times.
 >>
 >> --
 >> Kumar
 >
 >--
 >Rajesh Mirchandani
 >Developer Relations Engineer
 >BEA Support
 >
 >

Similar Messages

Multiple Orders with Different reasons on a Single day

Hi,
I am recently learning Device Management of IS-U Electricity. Now I have a problem with meter reading orders generated at the time of periodic meter reading with reason 01 and different system generated orders with reasons like 22, 21 , 16 and 11 which are the orders get created internally based on device replacement and modification.
If the scheduled meter reading date lies on the day or the day before of device replacement or modification, the meter reading for the periodic order is getting prorated based on the meter reading entered at the time of replacement or modification. This is what I dont want.
Is it possible to have multiple orders with different reasons on the same date? Any configuration changes are welcome.
- Arghya

Hi,
You can acheive this using following config changes.
SAP Utilities --> Device Managment -->Meter Reading --> Meter Reading Order -->Order Creation --> Define Automatic Interpolation for Meter Reading Reason.
Uncheck the 'Auto Interpolation' flag for Meter Reading reason 01.
This will not use the Replacement or Modifiaction read.
Let me know if anything more is reuiqred.
Thanks and Regards,
Ranjit Thakur.

Maintain same customer number twice with different GUIDs

Recently, R3 refreshed, but CRM not. After refresh R3 is having few customer & product numbers, which were same as earlier. That means those customers & products already exist in CRM. I run initial load for customizing & master data from R3 to CRM.
Now, I can see existing product number can be downloaded from R3 & result is same product number present twice in CRM with different GUIDs.
For customer, I am not able to download existing customer number via initial load. I am getting mapping error & error description - "Customer number EKC3137 is already assigned to a business partner". Delta load also failed for same customer with error - "Business partner with GUID 15ECAD322FDA074BB8B125DEDB4194DB does not exist". I checked & found existing entry in CRM is having different GUID for this customer.
Can anyone suggest how to download this customer with new GUID, keeping same customer with different GUID. This means expected result is same customer number maintained twice with two different GUIDs. Definitely old customer can not be updated from R3, but new one can be updated in future.
Regards,
Soumya

Hi.
Everytime you do a not simultaneous client copy you will get this inconsistencies on middleware data.
You can correct this as described below:
CUSTOMERS:
Apply note 609766 in order to create a report that will correct the customers Guids on tables: R/3: CRMKUNNR and CRM: CRMM_BUT_CUSTNO .
MATERIAL:
R/3 table that contains CRM product guid: NDBSMATG16
CRM table: COMM_PRODUCT
SAP recomends to delete all products and replicate them again: COM_PRODUCT_DELETE_SINGLE
Possible problem if you also have price condition tables on CRM (the product Guids will be the old ones so yoiu will have to download all pricing data again).
CONTACT PERSONS:
R/3: CRMPARNR
CRM: CRMM_BUT_CONTNO
Apply note 703322 and run report Z_OSS_000400_2004 on R/3 and corrects the inconsistencies.
Regards.
Susana Messias

Post down payment with different currency from request with F-48

Hi all,
I have a problem when I try to post a vendor down payment with the transaction F-48. The down payment request currency is EUR but I want to do the payment with USD. If I put in the field Currency/Rate USD the transaction F-48 show the message u201CNo suitable down payment request existu201D, but if I put the currency EUR the down payment request appears but I just can post it with EUR.
Is it possible to select the down payment request in EUR and post it with USD using the F-48 transaction?
Best regards,
Miguel

Hello,
I have the same challange like Miguel in the original thread:
"Is it possible to select the down payment request in EUR and post it with USD using the F-48 transaction?"
Please let me know how to manage this case in SAP.
Kind regards
Zarko

Call a service twice with different values

Hi,
I have two DropDownBoxes I want to fill with the service Helpvalues.GetList with different values. So I call the service in the init method. But then the second call overwrites the first call.
I thought about adding my own value attributes in my view but I get an error when I assign a ComplexType to the attributes.
Thank you
Julia

Hi Julia,
I think your DropDownboxes referring to same context.That is why your second call over writes the first one.
use 2 local context nodes ,fill them seperately from your service calls.

How to stream one table twice (with different names) in another schema ?

hello guys,
i have to replicate one table (TAB_1) from one schema (SCH_1) on source database (DB_1) twice to schema (SCH_2) on target database (DB_2) with two different names (TAB_1 and TAB_1_SHORT). TAB_1_SHORT on target db should be a subset (eg. WHERE STATUS = 1) of TAB_1 !
how to do ? can anyone help me ?
i tried to realize that this way:
1) creating 1 capture process with 1 table rule on source db (without any subset rules to capture all changes) for table TAB_1
2) creating a propagation process without any rules
3) creating 1 apply process with a table rule for table TAB_1 without any subset_rule but with schema transformation from SCH_1 to SCH_2 (DBMS_STREAMS_ADM.RENAME_SCHEMA) => this works correct !
4) creating a subset_rule (WHERE STATUS = 1), a schema transformation from SCH_1 to SCH_2 (DBMS_STREAMS_ADM.RENAME_SCHEMA) and a tablename transformation from TAB_1 to TAB_1_SHORT (DBMS_STREAMS_ADM.RENAME_SCHEMA) for table TAB_1_SHORT => doesn`t work, no errors posted in dba_apply_error !
in another try, i tried to transform the table- and the schemaname in the capture process, with the effect, that my first table TAB_1 wouldn`t be streamed again.
i`m not sure, what is wrong. i think it must be possible to stream a table to two different targettables in the same schema on another db, isn`t it ?
hopefully greetings
Flo

Hello
Adding a normal table rule and also a subset rule would not work since the rule would be evaluated only once in the positive rule set. If the normal rule is evaluated first then the subset rule and rest of the rules would not be evaluated at all hence this would not work.
This can be done using either of the following methods:
Method 1:
     1. Use the declarative transformation on the capture/apply and rename the schema from SCH_1 to SCH_2.
     2. Now, on the apply site, set a DML Handler for SCH_2.TAB_1
     3. In DML Handler perform the following:
          a. get the column value for STATUS
          b. check if the value for STATUS=1, if yes then modify the object name to TAB_1_SHORT and execute the LCR.
          c. else do not modify the object name (leave it as it is, TAB_1) and execute the LCR.
Method 2:
     1. Add a DML Handler for SCH_1.TAB_1
     2. In the DML Handler perform:
          a. use set_object_owner method of LCR$_ROW_RECORD to rename the owner to SCH_2
          b. get the column value for STATUS
          c. check if the value for STATUS=1, if yes then modify the object name to TAB_1_SHORT and execute the LCR.
          d. else do not modify the object name (leave it as it is, TAB_1) and execute the LCR.
Please let me know if you need sample code.
Thanks,
Rijesh

Can one ODI procedure be used twice with different option in one package?

I have a procedure with three check box type options. This procedure is used twice in a package. I tried to set options differently in the package, but once I set up the options for the second call, the first one will be updated to the same as the second one automatically. Is the option supposed be used as parameter? If it is true, why I cannot call procedure twice by using two different parameter settings?
Thanks

Create two scenarios of the same procedure. While generating scenarios change the options as necessary. Then in the package call the scenarios instead of the procedure. That should work.

Older computer on TC network shuts down, fixed with different router

I offer this as a solution to a problem with many possible reasons. It seems the router part of my Time Capsule was causing me problems. Using an old LinkSys router and making the Time Capsule be just a hard drive seems to have fixed my problem.
The situation is this: have been using a home network for three years with two wireless newer laptops and an older G4 machine as my base station with wired connections to printer, scanner, Time Capsule, and external hard drives, etc. One main use of all this is to archive photos from my laptop to an external hard drive connected to the G4 machine. A few months ago, it seemed that the G4 would die from a kernal panic whenever I tried to transfer 2 gigabytes or more of photo files. The G4 has an upgraded chip so it can run Leopard 10.5 but otherwise is the same old machine with a bus speed of 133 mHz, etc. Also, the hard drives could have problems, or repeated communication problems could have corrupted some software.
I finally decided to do a clean re-install of Leopard and that seemed to fix the problem for a while, but lately the G4 simply shut itself down with what seemed like little provocation. After careful diagnosis (and some time passing during which time whatever the disease is could have gotten worse), I narrowed the issue to one simple Finder task.
When using the laptop (wirelessly) to browse folders on one of the external hard drives wired to the G4, it would start to show me the files, but hang up, freeze and shut down if I probed folders (of 25 to 50 large jpeg files) too quickly. However, if I went to the G4 console and performed the same browse of folders, there was no problem, so I couldn't blame the G4 itself or the hard drives.
I suspect the Time Capsule router side is somehow not making allowances for the age and speed difference of the two machines on the network, or else is otherwise simply sick. Anyway, using an old LinkSys wireless router with the G4 and, with the help of hints and instructions here, keeping the Time Capsule as a hard drive only so my Time Machine backups can continue, seems to have solved my problem.
Once again, I can browse my archive hard drives to my heart's content and send several gigabytes worth of photo image files from the wireless laptop to the external hard drives served by the G4 and have no problem doing it. I am sure the official answer would have been to take the old G4 behind the barn and shoot it as it is now about 10 years old, but it is doing just fine as a base station server and it looks like it has a few more years yet to go.
I hope this helps someone with a similar problem.

Video: Nvidia Geforce 9600M GT
If you have a recent nVidia driver installed, you might want to check to see if you have either of these two modules loaded - check in the nVidia console:
PhysX, or 3D Stereovision. If you have them, definitely disable 3D Stereo, and test. If no improvement, disble PhysX and test.
Also, try adjusting your Hardware Acceleration. If Max, set to Min and test. If Min, set to Max and test. If either helps, try incrementing up, or down, until it no longer helps.
Last, check your OpenGL settings. If ON, turn OFF. If OFF, turn ON.
It appears that you have a laptop. Is that correct?
Good luck,
Hunt

Permissions - "everyone" group twice with different rights

Hi,
I found a couple of permission threads on the web and in here, but none seem to hit precisely what I experience.
Since I was already reading about problems upgrading/migrating from Tiger to Leopard, I was taking the precautious extra step and cloned my hard drive using Tiger 10.4.10 and Carbon Copy Cloner to an IEEE 1394 drive, after which I installed Leopard from scratch. Everything went well until the point I copied back my stuff into the respective folders (not overwriting the 1st-level home folders, e.g. Documents). Despite I selected that the external drive shall ignore permissions, it obviously created a permission mess on the internal drive on those files/folders. Permission-wise the files/folders looked like the following:
everyone - Custom
(unknown) - Custom <--- Not every file or folder
Phoenix (Me) - Read & Write
staff - Read Only <--- Not every file or folder
everyone - Read Only <--- Not every file or folder
The result is that as long as there is the "everyone" group in there with the "Custom" permissions, I am unable to change (e.g. rename) those files/folders.
If the "everyone" group is listed twice, I need to do the following 3 steps to straighten the permissions again:
1. Set "everyone - Custom" to "everyone - No Access"
2. Set the "everyone - Read Only" also to "everyone - No Access" (the second entry disappears at that point)
3. Set the remaining "everyone" group to "Read Only" as it was meant to be
Also, the "(unknown)" user seems not to disappear when clicking the "-" button, but disappears afterwards when doing the first of the above-mentioned 3 steps.
Though I managed to change the permissions on the items itself to just contain the 700 or 755 permissions, I was not successfully removing the "everyone - Custom" group or the "(Unknown)" users when using the "Apply to enclosed items" option for the sub-items. In fact, it appears to just sets the permissions to the 1st-level sub-folders skipping the files, but leaving the "Custom" and "(Unknown)" entries in there.
*After this long, but required introduction, here my question:*
Is there a tool, which is relatively simple to use to remove ALL permission entries and then after that adds the default permissions on it?
A script with "chmod" would also be fine. You may call me lazy, but I find it just nasty to change all 10s of 1000s of files basically one-by-one manually using the 3 steps for each file/folder.
Kind Regards,
Jan
PS: The issue seems to be ONLY with the old copied Tiger files. New files appear to get the correct permissions.

Question is archived and cannot be answered anymore.

Same circuit twice with different results

I've been having some trouble having Multisim match a circuit I have modeled in MATLAB. During the troubleshooting process I put voltage probes on each wire used. The circuit portion in question involves an AC Voltage source connected to a resistor which is then connected to an inductor. I made a copy of the circuit and started from scratch. One of the circuits gives a voltage drop across the resistor, while the other one doesn't drop any voltage at all. I've checked all of the connections and they are all good. The only difference I can see is that one has the pins labeled 1 - 2 while the other is 2 - 1. Does anyone know what the problem is here? I shouldn't not be getting two different results for the same circuit.

Hi Jmerc,
Maybe you can post the circuits so that we can compare.
Tien P.
National Instruments

Scrap with different reasons in same storage location

HI Experts,
In one of the scenario; the plants gets scrap from different sources such as from production or from other mean. User wants to see the bifurcation of the certain quantity of the same in the same storage location. I have seen that we can maintain storage bin in Plant/sto view 1; but the constrain is one material-one bin. But user needs it as one material-more bins in the same storage location.
Please advice.

A further segregation of one material is either batch management or split valuation.
Both is not easy to achieve if your material is already active and has stock (this is discussed many times, so please search if you need more info on that)
You can only differentiate by bins if you use warehouse management, in MM it is as you already found out yourself, 1 location = 1 Bin per material

Advance payment and down payment with two diffierent tax code

HI expert!!!
i have one scenario that advance payment and down payment with different tax code.
in this time, advance payement post to vendor with po number, we do not know how to use tax code V1(deductable tax) or VF(Non-deductable tax), so we post advance payement amount by tax code V1(deductable) even though the amount included both. but we must know how amount is defined deductable tax or non-deductable tax when invoice.
when we want to post down payment with VF , we could not post it because advance payement posted with V1 tax code.
this is main problem with my scenario.
and as i know, can i post two advance payement to same vendor and same po item?, i can't do it with my system.
only one advacne payment is possible with one vendor and one po item. or amount of advance payment is all cleared by down payment, then i can post another advance payment to same vendor. is it standard process with po?
thank you in advance!!

hi,
As per my knowledge their is no difference between advance payment and downpayment.
and tax code is used for taxes purpose not for the payment terms.
taxcode is created in ftxp.and related percentages are maintained in fv11.
ex:-
if i want excise duty - 10% on basic value
education cesse 2% on excise duty
sec.education cesses 1% on excise duty
then fitst i have to create 3 condition types and that 3 condition types are used in my taxprocedure and that taxprocedure is assigned to country code..
after that i am created one taxcode in ftxp like v1= exciseduty10%educatiocess2%sec.edu.cesses1% with this description.
and given the values for that conditions in fv11.
and used that v1 taxcode in your p.o in invoice tab.
and payment terms are came from vendor not from taxcode.
Thanking you.

Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff path

$ dmesg -l err
[ 6.330201] systemd[1]: Device dev-disk-by\x2duuid-d527fcab\x2d1897\x2d46a1\x2d8324\x2d18de507f4993.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache0 and /sys/devices/virtual/block/bcache2
[ 6.332384] systemd[1]: Device dev-disk-by\x2dlabel-raid0.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache2 and /sys/devices/virtual/block/bcache1
[ 6.334041] systemd[1]: Device dev-disk-by\x2duuid-d527fcab\x2d1897\x2d46a1\x2d8324\x2d18de507f4993.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache0 and /sys/devices/virtual/block/bcache1
[ 6.730564] systemd[1]: Device dev-disk-by\x2dlabel-raid0.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache2 and /sys/devices/virtual/block/bcache3
[ 6.732213] systemd[1]: Device dev-disk-by\x2duuid-d527fcab\x2d1897\x2d46a1\x2d8324\x2d18de507f4993.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache0 and /sys/devices/virtual/block/bcache3
[ 6.997304] systemd[1]: Device dev-disk-by\x2dlabel-jabod.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc3 and /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf3
[ 6.999960] systemd[1]: Device dev-disk-by\x2duuid-0d19cfc3\x2d7588\x2d4c19\x2db85e\x2dbf3a3db2d4a0.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc3 and /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf3
[ 7.003235] systemd[1]: Device dev-disk-by\x2dlabel-raid1.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 and /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf1
[ 7.005881] systemd[1]: Device dev-disk-by\x2duuid-99fd7889\x2dde7a\x2d4b30\x2d9745\x2d8ccb2b1ee75d.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 and /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf1
[ 7.194594] systemd[1]: Device dev-disk-by\x2dlabel-aroot.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf4 and /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sde/sde1
[ 7.197369] systemd[1]: Device dev-disk-by\x2duuid-3873d8ba\x2d9472\x2d4d92\x2dab0d\x2de94574bd0eae.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf4 and /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sde/sde1
[ 7.207859] systemd[1]: Device dev-disk-by\x2dlabel-raid1.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 and /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sde/sde3
[ 7.210477] systemd[1]: Device dev-disk-by\x2duuid-99fd7889\x2dde7a\x2d4b30\x2d9745\x2d8ccb2b1ee75d.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 and /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sde/sde3
[ 7.240459] systemd[1]: Device dev-disk-by\x2dlabel-aroot.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf4 and /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb2
[ 7.243114] systemd[1]: Device dev-disk-by\x2duuid-3873d8ba\x2d9472\x2d4d92\x2dab0d\x2de94574bd0eae.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf4 and /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb2
[ 8.062829] systemd[1]: Device dev-disk-by\x2dlabel-jabod.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc3 and /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb4
[ 8.065328] systemd[1]: Device dev-disk-by\x2duuid-0d19cfc3\x2d7588\x2d4c19\x2db85e\x2dbf3a3db2d4a0.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc3 and /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb4
I've been getting this since I upgraded systemd last week. I tried fixing some of these by removing partitions with the same label that I wasn't using, which worked. The reason I have so many partitions with the same label is due to btrfs. Each partition that makes up a volume in btrfs has the same label. Apparently systemd doesn't like this.
Everything on my system seems to be working fine, however I would like to stop these errors since they are annoying/scary, but without having to reduce all my volumes to single.
Last edited by nstgc (2015-04-26 15:53:20)

I'm running with a wired-only set up. I'll have to wait for the weekend to look into the wireless angle, however I doubt that is the cause for me.
Following dront78's example below is the output of "# hwinfo --partitions"
75: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: bdUI.SE1wIdpsiiC
Parent ID: 3OOL.7ppt9e3ai+9
SysFS ID: /class/block/sda/sda1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sda1
Device Files: /dev/sda1, /dev/disk/by-id/ata-KINGSTON_SH103S3240G_50026B7234025EC8-part1, /dev/disk/by-id/wwn-0x6829766019904589826x-part1, /dev/disk/by-partuuid/77f1354c-3b20-454d-ba60-9dbab9bc8640, /dev/disk/by-uuid/ff387510-d0ad-498f-8d1b-576b26ed103e
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #74 (Disk)
76: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: 2pkM.SE1wIdpsiiC
Parent ID: 3OOL.7ppt9e3ai+9
SysFS ID: /class/block/sda/sda2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sda2
Device Files: /dev/sda2, /dev/disk/by-id/ata-KINGSTON_SH103S3240G_50026B7234025EC8-part2, /dev/disk/by-id/wwn-0x6829766019904589826x-part2, /dev/disk/by-partuuid/44596381-4cfe-4a2d-8e7b-f6427cc089d0
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #74 (Disk)
77: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: W__Q.SE1wIdpsiiC
Parent ID: 3OOL.7ppt9e3ai+9
SysFS ID: /class/block/sda/sda3
Hardware Class: partition
Model: "Partition"
Device File: /dev/sda3
Device Files: /dev/sda3, /dev/disk/by-id/ata-KINGSTON_SH103S3240G_50026B7234025EC8-part3, /dev/disk/by-id/wwn-0x6829766019904589826x-part3, /dev/disk/by-partuuid/c9b404ec-f407-4081-a69c-9b10360d4cf7
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #74 (Disk)
78: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: z9FV.SE1wIdpsiiC
Parent ID: 3OOL.7ppt9e3ai+9
SysFS ID: /class/block/sda/sda4
Hardware Class: partition
Model: "Partition"
Device File: /dev/sda4
Device Files: /dev/sda4, /dev/disk/by-id/ata-KINGSTON_SH103S3240G_50026B7234025EC8-part4, /dev/disk/by-id/wwn-0x6829766019904589826x-part4, /dev/disk/by-partuuid/69c0972d-51ed-429c-acea-6e1afd7ebb1f
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #74 (Disk)
80: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: h4pj.SE1wIdpsiiC
Parent ID: WZeP.bTSLTpVNGx8
SysFS ID: /class/block/sdb/sdb1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdb1
Device Files: /dev/sdb1, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33388736-part1, /dev/disk/by-id/wwn-0x17950130428369588225x-part1, /dev/disk/by-uuid/2c0f1039-2d4b-4f75-8fa4-529d19cd18fc
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #79 (Disk)
81: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: 8G3o.SE1wIdpsiiC
Parent ID: WZeP.bTSLTpVNGx8
SysFS ID: /class/block/sdb/sdb2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdb2
Device Files: /dev/sdb2, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33388736-part2, /dev/disk/by-id/wwn-0x17950130428369588225x-part2, /dev/disk/by-label/aroot, /dev/disk/by-uuid/3873d8ba-9472-4d92-ab0d-e94574bd0eae
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #79 (Disk)
82: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: bRJs.SE1wIdpsiiC
Parent ID: WZeP.bTSLTpVNGx8
SysFS ID: /class/block/sdb/sdb3
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdb3
Device Files: /dev/sdb3, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33388736-part3, /dev/disk/by-id/wwn-0x17950130428369588225x-part3, /dev/disk/by-label/old-raid1, /dev/disk/by-uuid/dfa989d8-edac-4c7e-b6fc-45237e6a0ebc
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #79 (Disk)
83: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: 2dZw.SE1wIdpsiiC
Parent ID: WZeP.bTSLTpVNGx8
SysFS ID: /class/block/sdb/sdb4
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdb4
Device Files: /dev/sdb4, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33388736-part4, /dev/disk/by-id/wwn-0x17950130428369588225x-part4, /dev/disk/by-label/jabod, /dev/disk/by-uuid/0d19cfc3-7588-4c19-b85e-bf3a3db2d4a0
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #79 (Disk)
85: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: mX79.SE1wIdpsiiC
Parent ID: _kuT.rgQvtxWxfg6
SysFS ID: /class/block/sdc/sdc1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdc1
Device Files: /dev/sdc1, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WMAW31235179-part1, /dev/disk/by-id/wwn-0x4611505914592251905x-part1, /dev/disk/by-uuid/80780835-de4b-462c-b7f0-2b389d3e2c2f
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #84 (Disk)
86: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: DjND.SE1wIdpsiiC
Parent ID: _kuT.rgQvtxWxfg6
SysFS ID: /class/block/sdc/sdc2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdc2
Device Files: /dev/sdc2, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WMAW31235179-part2, /dev/disk/by-id/wwn-0x4611505914592251905x-part2, /dev/disk/by-label/raid1, /dev/disk/by-uuid/99fd7889-de7a-4b30-9745-8ccb2b1ee75d
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #84 (Disk)
87: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: gudH.SE1wIdpsiiC
Parent ID: _kuT.rgQvtxWxfg6
SysFS ID: /class/block/sdc/sdc3
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdc3
Device Files: /dev/sdc3, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WMAW31235179-part3, /dev/disk/by-id/wwn-0x4611505914592251905x-part3, /dev/disk/by-label/jabod, /dev/disk/by-uuid/0d19cfc3-7588-4c19-b85e-bf3a3db2d4a0
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #84 (Disk)
88: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: 74uL.SE1wIdpsiiC
Parent ID: _kuT.rgQvtxWxfg6
SysFS ID: /class/block/sdc/sdc4
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdc4
Device Files: /dev/sdc4, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WMAW31235179-part4, /dev/disk/by-id/wwn-0x4611505914592251905x-part4, /dev/disk/by-label/old-aroot, /dev/disk/by-uuid/b396dd50-e3f1-4b74-8cac-7d8d79a75386
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #84 (Disk)
90: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: r_Ra.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd1
Device Files: /dev/sdd1, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part1, /dev/disk/by-id/wwn-0x14865109125905272832x-part1, /dev/disk/by-partlabel/Microsoft\x20reserved\x20partition, /dev/disk/by-partuuid/f3e9ce24-988d-40ef-bd5c-6313c808bef2
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
91: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: IAie.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd2
Device Files: /dev/sdd2, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part2, /dev/disk/by-id/wwn-0x14865109125905272832x-part2, /dev/disk/by-partlabel/Basic\x20data\x20partition, /dev/disk/by-partuuid/f3344931-99c3-11e4-8601-806e6f6e6963, /dev/disk/by-uuid/30F403F0F403B75E
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
92: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: lLyi.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd3
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd3
Device Files: /dev/sdd3, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part3, /dev/disk/by-id/wwn-0x14865109125905272832x-part3, /dev/disk/by-partlabel/EFI\x20system\x20partition, /dev/disk/by-partuuid/ffbaa0cc-99c7-11e4-8625-806e6f6e6963, /dev/disk/by-uuid/0DE5-0CB0
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
93: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: CXCn.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd4
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd4
Device Files: /dev/sdd4, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part4, /dev/disk/by-id/wwn-0x14865109125905272832x-part4, /dev/disk/by-partlabel/Basic\x20data\x20partition, /dev/disk/by-partuuid/ffbaa0b6-99c7-11e4-8625-806e6f6e6963, /dev/disk/by-uuid/FE2648382647EFE7
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
94: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: fiSr.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd5
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd5
Device Files: /dev/sdd5, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part5, /dev/disk/by-id/wwn-0x14865109125905272832x-part5, /dev/disk/by-label/flbck, /dev/disk/by-partuuid/bd84f197-066e-4b9e-bf9b-b0b3a4090cde, /dev/disk/by-uuid/832bcc8d-836e-4b4e-8d9c-0a19f5bcf7dd
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
95: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: 6uiv.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd6
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd6
Device Files: /dev/sdd6, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part6, /dev/disk/by-id/wwn-0x14865109125905272832x-part6, /dev/disk/by-partuuid/8f77bc79-ba57-462e-8beb-d09db5c77490
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
96: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: oKuO.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd7
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd7
Device Files: /dev/sdd7, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part7, /dev/disk/by-id/wwn-0x14865109125905272832x-part7, /dev/disk/by-partuuid/7ca3eb27-d198-4915-9c71-e96fa7a34d8b, /dev/disk/by-uuid/fd43f1bd-9f52-41b7-badc-4ab7881473ee
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
97: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: GW8T.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd8
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd8
Device Files: /dev/sdd8, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part8, /dev/disk/by-id/wwn-0x14865109125905272832x-part8, /dev/disk/by-partuuid/550f9e19-c0ec-4474-9e98-84c727854158
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
98: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: cPdt.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd10
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd10
Device Files: /dev/sdd10, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part10, /dev/disk/by-id/wwn-0x14865109125905272832x-part10, /dev/disk/by-label/bckup, /dev/disk/by-partuuid/de7eaa1e-66b0-4058-ad71-d0f8ea470b2f, /dev/disk/by-uuid/723d7788-8514-4777-8e07-e0faa48c9a83
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
100: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: wRm+.SE1wIdpsiiC
Parent ID: u5Pc.jfv0tLKpnVA
SysFS ID: /class/block/sde/sde1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sde1
Device Files: /dev/sde1, /dev/disk/by-id/ata-ST2000NM0053-1C1175_Z1X48TVG-part1, /dev/disk/by-id/wwn-0x9832618751734861824x-part1, /dev/disk/by-label/aroot, /dev/disk/by-uuid/3873d8ba-9472-4d92-ab0d-e94574bd0eae
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #99 (Disk)
101: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: Nd04.SE1wIdpsiiC
Parent ID: u5Pc.jfv0tLKpnVA
SysFS ID: /class/block/sde/sde2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sde2
Device Files: /dev/sde2, /dev/disk/by-id/ata-ST2000NM0053-1C1175_Z1X48TVG-part2, /dev/disk/by-id/wwn-0x9832618751734861824x-part2, /dev/disk/by-uuid/aa19d2cf-e59d-4277-a5e6-d0078ede6d3b
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #99 (Disk)
102: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: qoG8.SE1wIdpsiiC
Parent ID: u5Pc.jfv0tLKpnVA
SysFS ID: /class/block/sde/sde3
Hardware Class: partition
Model: "Partition"
Device File: /dev/sde3
Device Files: /dev/sde3, /dev/disk/by-id/ata-ST2000NM0053-1C1175_Z1X48TVG-part3, /dev/disk/by-id/wwn-0x9832618751734861824x-part3, /dev/disk/by-label/raid1, /dev/disk/by-uuid/99fd7889-de7a-4b30-9745-8ccb2b1ee75d
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #99 (Disk)
103: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: H_WC.SE1wIdpsiiC
Parent ID: u5Pc.jfv0tLKpnVA
SysFS ID: /class/block/sde/sde4
Hardware Class: partition
Model: "Partition"
Device File: /dev/sde4
Device Files: /dev/sde4, /dev/disk/by-id/ata-ST2000NM0053-1C1175_Z1X48TVG-part4, /dev/disk/by-id/wwn-0x9832618751734861824x-part4
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #99 (Disk)
105: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: +u4R.SE1wIdpsiiC
Parent ID: LHfg.eZsVjjzwg10
SysFS ID: /class/block/sdf/sdf1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdf1
Device Files: /dev/sdf1, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33509457-part1, /dev/disk/by-id/wwn-0x8355873293896667137x-part1, /dev/disk/by-label/raid1, /dev/disk/by-uuid/99fd7889-de7a-4b30-9745-8ccb2b1ee75d
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #104 (Disk)
106: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: S4LV.SE1wIdpsiiC
Parent ID: LHfg.eZsVjjzwg10
SysFS ID: /class/block/sdf/sdf2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdf2
Device Files: /dev/sdf2, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33509457-part2, /dev/disk/by-id/wwn-0x8355873293896667137x-part2, /dev/disk/by-uuid/96fa47c5-061d-4849-8582-7186cc1695d2
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #104 (Disk)
107: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: vFbZ.SE1wIdpsiiC
Parent ID: LHfg.eZsVjjzwg10
SysFS ID: /class/block/sdf/sdf3
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdf3
Device Files: /dev/sdf3, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33509457-part3, /dev/disk/by-id/wwn-0x8355873293896667137x-part3, /dev/disk/by-label/jabod, /dev/disk/by-uuid/0d19cfc3-7588-4c19-b85e-bf3a3db2d4a0
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #104 (Disk)
108: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: NRrd.SE1wIdpsiiC
Parent ID: LHfg.eZsVjjzwg10
SysFS ID: /class/block/sdf/sdf4
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdf4
Device Files: /dev/sdf4, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33509457-part4, /dev/disk/by-id/wwn-0x8355873293896667137x-part4, /dev/disk/by-label/aroot, /dev/disk/by-uuid/3873d8ba-9472-4d92-ab0d-e94574bd0eae
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #104 (Disk)
i don't have time to look at this in detail this morning, but I will this afternoon.
Thank you for all the replies. Have any of you found this to actually be damaging?
[edit] In an effort to not be completely lazy, and because I was curious, I did check a bit into netctl. Running "$ netctl list" returned exactly nothing. I have no profiles.
[edit2]
I just ran "$ dmesg -l err" on my laptop and I'm not getting any errors.
Last edited by nstgc (2015-04-27 15:09:46)

Can I create and use 2 PKCS11 Providers, each with different config?

Here is the code I am running twice with different configFilePaths:
     setNssProvider(new SunPKCS11(getConfigFilePath()));
     Security.addProvider(nssProvider);
     Security.removeProvider("SunJSSE");
     Provider jsse = new com.sun.net.ssl.internal.ssl.Provider(nssProvider);
     Security.addProvider(jsse);
     keyStore = KeyStore.getInstance("PKCS11", nss);
     keyStore.load(null, ksParams.getKeyStorePassword().toCharArray());
I am getting a ProviderException, presumable where I create the SunPKCS11 instance:
     ProviderException: Secmod directory c:\nss\fips2db invalid, NSS already initialized with c:\nss\fips1db
Is it possible to run two PKCS11 Providers, with different configs, in the same address space?
Thank you,
Rob

reefedjib wrote:
Is there anyone else who could comment on my problem, here? I am really hoping that someone can point me to a solution.I realized I was using the same name in the config files. I changed it to be different and the same result is occurring.
ProviderException: Secmod directory c:\nss\fips2db invalid, NSS already initialized with c:\nss\fips1dbHere are my two config files:
name = NSSfips1
nssLibraryDirectory = c:\nss\lib
nssSecmodDirectory = c:\nss\fips1db
nssModule = fips
name = NSSfips2
nssLibraryDirectory = c:\nss\lib
nssSecmodDirectory = c:\nss\fips2db
nssModule = fipsAny word on this?
Thanks

RAC with different OS?

Hi
I want to add another cluster to my RAC with different OS (Windows 2003). And my clusters OS is "Suse 9". Can I do it or should I change Windows OS to Suse?
Regard

Hi
Thanks for your attention
I have a RAC with two cluster (Suse 9 OS). And I want to add another cluster with Windows 2003 OS. I don't have any problem with network setting (node connectivity) just I have problem with 'Oracle' user (user equivalence).
now my question:
Is a way to define the 'Oracle' user in Windows OS?
mean while I used the NFS for disk-sharing, and I can use a "MS Windows Services for NFS" for define my users and groups.
another question: Can I use different type of Linux like FreeBSD or RedHat?
Best Regards

Servers in cluster go down : twice with different reasons

Similar Messages

Maybe you are looking for