[solved] /etc/udev/rules.d/10-network.rules ignored

Hi.
I have 4 nics (eth0, eth1, eth2, eth3) mapped to MAC addresses in /etc/udev/rules.d/10-network.rules.
Some months ago, I had to symlink /etc/udev/rules.d/80-net-name-slot.rules to /dev/null in order to use these static names.
Now it doesn't work anymore (again and again and again) after a full update (kernel and I assume systemd). The "nic-names" are completely wrong. You call this "predictable". I call this "unpredictable". The only thing which is predictable is that after a kernel update, the network will stop working. It has been that way for months and months ... fortunately I don't update other machines anymore.
Was this non sense really necessary?
Anyway, if you could tell me what to do now to get my network rules applied again, I would really appreciate.
Right now all ethX/MAC are wrong and none of them gets an IP (had to set an IP manually to post here).
* I know what "predictable Network Interface Names" is about. I don't want this bullshit. It's much worse as it used to be. Keep it simple, folks!
Last edited by Agnelo de la Crotche (2013-03-27 07:14:05)

tomegun wrote:To narrow down the problem you are experiencing: What do you mean when you say that the names are "wrong"? Are they still eth0, eth1,... just in the wrong order, or are you actually seeing the "weird" new names given by udev?
To answer this question more precisely.
* with /etc/udev/rules.d/80-net-name-slot.rules => /dev/nul and /etc/udev/rules.d/10-network.rules posted earlier (in #4)
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether 00:0a:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether 00:06:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether 00:24:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
5: eth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether 00:1b:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
6: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT
link/ether 66:64:b3:6a:26:61 brd ff:ff:ff:ff:ff:ff
The rules are ignored.
* after deleting /etc/udev/rules.d/80-net-name-slot.rules
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp6s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether 00:0a:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
3: enp6s1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether 00:06:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
4: enp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether 00:24:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
5: enp4s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether 00:1b:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
6: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT
link/ether a2:ee:ec:d1:65:2d brd ff:ff:ff:ff:ff:ff
The rules don't apply.
* with /etc/udev/rules.d/80-net-name-slot.rules => /dev/nul and after replacing eth0, eth1, eth2, eth3 with arbitrary names net0, net1, net2, net3 in /etc/udev/rules.d/10-network.rules
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: net1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether 00:24:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
3: net3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether 00:0a:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
4: net2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether 00:06:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
5: net0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether 00:1b:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
6: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT
link/ether ea:63:09:b7:1b:1b brd ff:ff:ff:ff:ff:ff
But the rules were applied in this case!
It solved the problem described originally. I think I was hit by the race condition after upgrating to kernel 3.8.4-1. This was actually my first 3.8 kernel.
With kernel 3.7, the rules were working even if the devices were named eth0, eth1, etc.
Those names don't work anymore, at least in my case.
Further I created this file for static ips:
# cat /etc/systemd/system/network.service
[Unit]
Description=Wired Static IP Connectivity
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-net0.device
After=sys-subsystem-net-devices-net0.device
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/sbin/ip link set dev net0 up
ExecStart=/sbin/ip addr add 192.168.101.9/24 dev net0
ExecStart=/sbin/ip link set dev net1 up
ExecStart=/sbin/ip addr add 192.168.102.9/24 dev net1
ExecStart=/sbin/ip link set dev net2 up
ExecStart=/sbin/ip addr add 192.168.104.9/24 dev net2
ExecStart=/sbin/ip link set dev net3 up
ExecStart=/sbin/ip addr add 192.168.105.9/24 dev net3
ExecStart=/sbin/ip route add default via 192.168.101.1
ExecStop=/sbin/ip addr flush dev net0
ExecStop=/sbin/ip link set dev net0 down
ExecStop=/sbin/ip addr flush dev net1
ExecStop=/sbin/ip link set dev net1 down
ExecStop=/sbin/ip addr flush dev net2
ExecStop=/sbin/ip link set dev net2 down
ExecStop=/sbin/ip addr flush dev net3
ExecStop=/sbin/ip link set dev net3 down
[Install]
WantedBy=multi-user.target
I disabled netcfg and enabled network.service.
Problem is solved now.

Similar Messages

Are /etc/udev/rules.d/86-hpmud* files obsolete?

For a while now, I keep getting the following errors during boot:
Sat Jan 21 14:25:13 2012: udevd[148]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/86-hpmud-hp_laserjet_professional_p1102w.rules:9
Sat Jan 21 14:25:13 2012: udevd[148]: invalid rule '/etc/udev/rules.d/86-hpmud-hp_laserjet_professional_p1102w.rules:9'
... (repeat for every 86-hpmud-* file in that folder)
I found an (ancient) bug report from 2009 with the subject "hplip: obsolete udev rules files are not removed on upgrades", so I assume they're obsolete, but I've only recently starting seeing this problem, which wouldn't jive with a 3-year old issue.
Can I safely delete these files, assuming that their contents has been replaced with entries in the /lib/udev/rules.d tree? I am not that well-versed in udev, unfortunately....

OK - I backed them up and moved them out of /etc/udev/rules.d.
Confirming nothing broke is a bit of a problem right now. Printing is hit & miss from my laptop to my wireless HP P1102w printer at the best of times. I haven't figured out what the real issue is there, but since printing to other HPs works fine, I'll probably have to blame the printer or HPLIP. I wish HP would simplify their software and made simple drivers. I just need to print, I don't need all that hp-toolbox junk. I'll confirm this when I have a chance to print to a different HP printer.

3 unable to open '/etc/udev/rules.d/':m error during booting

After a recent upgrade to the kernel26-2.6.28.5-1-i686, I got the above error during booting in one of the laptop.
My search did not give any positive solution for this till now. I read that now udev gets its rules from /lib/udev/rules.d.
But still rules files in /etc/udev/rules.d and /lib/udev/rules.d are different. I know that any symllink work around will not work in this case, I tried but as expected the error message appears again.
So, I roll back to kernel26-2.6.28.4-1-i686 and everything back to normal.
Any Idea to resolve this? (package is not broken as I use the same mirror for another PC and in that I am not getting any error)
Last edited by kgas (2009-02-19 16:10:23)

This issue got resolved on its own with the latest kernel (kernel26-2.6.28.6-1-i686) update. I will leave this topic for some more time to see others response...

[solved] My udev rule for my Android phone doesn't work, not sure why

I have the HTC G1 Android phone and I'm trying to get a udev rule working for it. This is my rule ...
/etc/udev/rules.d/50-android.rules
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0bb4", MODE="0666", NAME=="android"
... but when I connect my phone, /dev/android doesn't appear. 0bb4 is correct ...
/sys/class/usb_device/usbdev5.2/device/idVendor
0bb4
... so what's going on?
Last edited by synthead (2008-11-28 15:19:09)

There is, but I can already use it that way. I'm learning how to code in java so I can develop applications for it. There's a feature in the SDK where you can install and run your code on your Android device fairly seamlessly. You literally hit "Run" and a few moments later, your phone's going to town. But for this to work, permissions need to be set (0666). But my udev rule does nothing and I dont understand why.
This is where I got this information: http://code.google.com/android/intro/de … cehardware

Oh god I overwrote /etc/udev/rules.d/90-hal.rules

I accidentally sudo overwrote this file with garbage. I haven't rebooted yet. What was in here? Is it important? How do I get it back?
Thanks!

If it was something in that directory, the sizes should be different than mine. This is what I have:
ls -l /etc/udev/rules.d/
total 52
-rw-r--r-- 1 root root 1071 2008-09-24 07:07 60-pcmcia.rules
-rw-r--r-- 1 root root 390 2009-03-07 15:42 75-cd-aliases-generator.rules.optional
-rw-r--r-- 1 root root 2403 2009-03-07 15:42 75-persistent-net-generator.rules.optional
-rw-r--r-- 1 root root 8039 2009-03-07 15:42 81-arch.rules
-rw-r--r-- 1 root root 82 2008-11-30 08:51 90-hal.rules
-rw-r--r-- 1 root root 28 2008-10-19 06:35 99-fuse.rules

Firewall: The invalid rule and all subsequent rules were skipped.

Hi All,
As a web developer, I have had some experience administering Linux, Solaris, Windows, but I am new to OSX.
I have a problem with the firewall I need help with.
Here are the symptoms:
1) Address Groups: Besides any, I have an address group called Admin, it contains my home and work ip address. Other address group is for LAN. When inspecting the properties of a group, the interface tells me 'valid IP address' or 'address range from .. to ..'. This seems OK
2) When editing an Advanced Rule, I can select one of the Address Groups just created for a source/destination. I save the configuration, resulting in a error 'Error while writing settings (cannot apply one or more rules - detail in log)'.
Opening the editor for the rule again, the field with the source/destination now has a small note under it: 'Invalid IP address, range or group). This is my first problem.
3) I have now deleted all Advanced Rules and deselected the ones I cannot delete. Still the error message 'Error while writing settings...'. The log offers no help at all:
May 23 10:17:07 Shaman servermgrd: servermgr_ipfilter:ipfw config:Notice:Disabled firewall
May 23 10:17:07 Shaman servermgrd: servermgr_ipfilter:ipfw config:Info:Finished generating rules in 2 ms
May 23 10:17:07 Shaman servermgrd: servermgr_ipfilter:ipfw config:Notice:Flushed rules
May 23 10:17:07 Shaman servermgrd: servermgr_ipfilter:ipfw config:Error:Failure code returned by ipfw command: 64, message: 'Line 18: recv, xmit, via require interface name or address\n'
May 23 10:17:07 Shaman servermgrd: servermgr_ipfilter:ipfw config:Error:The invalid rule and all subsequent rules were skipped.
May 23 10:17:07 Shaman servermgrd: servermgr_ipfilter:ipfw config:Notice:Enabled firewall
I cannot find out what is wrong from this output.
3) At this point I may as well turn the firewall off, for instance I have given access to http/ssh/ftp to group 'any', but they can in fact reach any port at all.
Thanks in advance for any help or suggestions,
Sander
2GHz PowerPC G5 Mac OS X (10.4.6)

Well, the obvious question is what does line 18 say?
The log clearly states that the rule on that line is the one it's having problems with:
May 23 10:17:07 Shaman servermgrd: servermgr_ipfilter:ipfw config:Error:Failure code returned by ipfw command: 64, message: 'Line 18: recv, xmit, via require interface name or address\n'
Check /etc/ipfilter/ipfw.conf for the configuration file in question.

Business Rule Error: Fact not found in the rule engine working memory, rule

I am trying to create a simple decision table with an input(ValidateInput) and a output(ValidateOutput). The input and output schemas have unbounded and nested elements(Parent-child relationship). When I create a condition(specific condition on input) and in the action I am asserting the output object. But when I run using EM it throws the following exception. It would be helpful if somebody could tell me what could be the problem. Please note when I set the output as ValidateInput object then it runs fine. Also it executes fine with ValidateOutput if it doesn't have unbounded(List) element inside it.
Error Message: {http://xmlns.oracle.com/OracleRules10/OracleRules10_DecisionService_1}operationErroredFault
Fault ID rules:211
Fault Time Jun 18, 2011 10:45:13 AM
Non Recoverable Business Fault :
Fact not found in the rule engine working memory, rule session execution failed. The rule session 270013 failed because an instance of the fact com.example.customer.ValidateResponse could not be found in the working memory of the rule session. This is most likely a rule modeling error. The decision service interaction expects the fact instance to exist in the working memory of the rule session. Check the rule actions in rule designer and make sure that a fact of the expected type is being asserted. If the error persists, contact Oracle Support Services. 270013
Edited by: reachsky on 18 Jun, 2011 9:57 AM

It's working now..I had to use Global variable to declare child element of the output variable and use the same during action.

How to update the bucketset of business rules in MDS through Rules SDK

How to update the bucketset of business rules in MDS through Rules SDK.
Any sample code which will help me........ :)
Is it possible to expose a Business Rule as webservice which was created with the help of Java fact?
Edited by: 984804 on Jan 29, 2013 6:12 PM

FYI, the output of this call returns something like:
<?xml version="1.0" encoding="UTF-8"?>
<queryplan>
    <union>
        <fullOuterJoin>
            <statement index="1">SELECT 'FY' || to_char(SALES.invoice_date,'yy'), count( distinct SALES.inv_id) FROM SALES GROUP BY 'FY' || to_char(SALES.invoice_date,'yy')</statement>
            <statement index="2">SELECT 'FY' || to_char(SALES.invoice_date,'yy'), sum(INVOICE_LINE.nb_guests) FROM SALES, INVOICE_LINE, SERVICE_LINE, SERVICE WHERE ( SALES.INV_ID=INVOICE_LINE.INV_ID ) AND ( INVOICE_LINE.SERVICE_ID=SERVICE.SERVICE_ID ) AND ( SERVICE.SL_ID=SERVICE_LINE.SL_ID ) AND ( SERVICE_LINE.service_line = 'Accommodation' ) GROUP BY 'FY' || to_char(SALES.invoice_date,'yy')</statement>
        </fullOuterJoin>
        <fullOuterJoin>
            <statement index="3">SELECT 'FY' || to_char(SALES.invoice_date,'yy'), count( distinct SALES.inv_id) FROM SALES GROUP BY 'FY' || to_char(SALES.invoice_date,'yy')</statement>
            <statement index="4">SELECT 'FY' || to_char(SALES.invoice_date,'yy'), sum(INVOICE_LINE.days * INVOICE_LINE.nb_guests * SERVICE.price) FROM SALES, INVOICE_LINE, SERVICE WHERE ( SALES.INV_ID=INVOICE_LINE.INV_ID ) AND ( INVOICE_LINE.SERVICE_ID=SERVICE.SERVICE_ID ) GROUP BY 'FY' || to_char(SALES.invoice_date,'yy')</statement>
        </fullOuterJoin>
    </union>
</queryplan>

Fact not found in the rule engine working memory,rule session executionfail

Hi
I'm getting this error on my BRE, the instance Id shows 'faulted' but other consectuctive web services are 'completed' successfully.
please advise how to fix it.
Error Message: {http://xmlns.oracle.com/zz_ValidationRules/zz_ValidationRules_DecisionService_1}operationErroredFault
Fault ID rules:417
Fault Time Aug 25, 2011 4:59:39 PM
Non Recoverable Business Fault :
Fact not found in the rule engine working memory, rule session execution failed. The rule session 130287 failed because an instance of the fact Response could not be found in the working memory of the rule session. This is most likely a rule modeling error. The decision service interaction expects the fact instance to exist in the working memory of the rule session. Check the rule actions in rule designer and make sure that a fact of the expected type is being asserted. If the error persists, contact Oracle Support Services. 130287
thanks,
Umesh
Edited by: user13664410 on Aug 25, 2011 2:19 PM

When i had this issue i overcame it by opening the Rule Editor->Deleting all existing facts that are imported->Close JDeveloper -> Delete the contents of .rulesdesigner directory in your workspace -> Restart JDeveloper -> Reopen Rule designer and re import all facts.
Also make sure that all the schemas that are used for Facts are valid ones.

5.3 upgrade delivered rules vs 5.2 rules

We recently upgraded to 5.3 and noticed there were delivered rules sent with the software. Are these rules different than the ones we used in 5.2 because I have role violations but no user violations and I can't figure this out....any advice?
Regards,
Greg

PROBLEM DESCRIPTION TO SAP: My 5.2 GRC AC system was upgraded to 5.3 in Oct 09. Since the upgrade, no user violations are showing/updating and I know for certain that the users have been assigned roles with conflicts. I would like to obtain a cleanup script to wipe the Business Process, Function, Function Authorization, Rule Set, and Risk rules so that I may reload them.
SAP RESPONSE: Unfortunately, at this time, we are unable to provide you scripts to perform the function you want. Doing direct table updates is not something that GRC is able to support at this time. I'm attaching a word document that provides you the table and field names for the application. Your Database Administrator and developers should be able to use this information to develope scripts to accomplish what you require.
MY RESPONSE: I have asked our DBA to look at the information you sent and he's informed me that he wouldn't know where to begin. Will this script work (script not attached).
SAP RESPONSE: I technically can't confirm that this will work. But the tables
did not change between 5.2 and 5.3.

Com.bea.p13n.rules.manager.RuleSetNotFoundException: The rule set with URI /segments/GlobalClassifications.rls could not be located by the class named com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager

Hi,
I am getting below exceptions in weblogic portal 10.3.5 which is upgraded from 10.3.4 portal. I have a datasync project .when try to run from workshop(eclipse IDE) getting below error.
com.bea.p13n.servlets.jsp.JspException: DivTag: The retrieved advice is incomplete. See the processing error list for more information.
com.bea.p13n.advisor.internal.AdviceImpl@299d48
Identifier: 1377808035572
Complete: true
Last Result: null
ProcessingError List:
(1) com.bea.p13n.advisor.internal.ProcessingErrorImpl@1504ee
Description: Exception evaluating ruleset.
Source: com.bea.p13n.rules.advislets.RulesAdvisletImpl@e6d518
Advisor: com.bea.p13n.advisor.internal.AdvisorImpl@b04a4e
Metadata: com.bea.p13n.common.internal.MetadataImpl@1de62ee
Name: UnmappedRulesAdvislet
Description: Advislet that can evalaute a ruleset and return the instantiated objects.
Author: BEA Systems
Version: com.bea.p13n.common.internal.VersionImpl@13130a2 Description: WLP 9.2 Number: 9.2, Build Number 1.
Parameters: {ruleset-name=/segments/GlobalClassifications.rls, ignore-rule-name=false}
User data: null
Exception: com.bea.p13n.rules.manager.RuleSetNotFoundException: The rule set with URI /segments/GlobalClassifications.rls could not be located by the class named com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.
at com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.getRuleSet(RuleSetPersistenceManager.java:408)
at com.bea.p13n.rules.manager.internal.ContextPool.<init>(ContextPool.java:149)
at com.bea.p13n.rules.manager.internal.ContextPoolFactory.getContextPool(ContextPoolFactory.java:214)
at com.bea.p13n.rules.manager.internal.RulesManagerImpl.getContext(RulesManagerImpl.java:480)
at com.bea.p13n.rules.manager.internal.RulesManagerImpl.evaluate(RulesManagerImpl.java:353)
at com.bea.p13n.rules.manager.internal.RulesManagerImpl.evaluateRule(RulesManagerImpl.java:194)
at com.bea.p13n.rules.manager.internal.RulesManager_jswjkk_EOImpl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
at com.bea.p13n.rules.manager.internal.RulesManager_jswjkk_EOImpl.evaluateRule(Unknown Source)
at com.bea.p13n.rules.advislets.RulesAdvisletImpl.getAdvice(RulesAdvisletImpl.java:190)
at com.bea.p13n.advisor.internal.AdvisorImpl.getAdvice(AdvisorImpl.java:74)
at com.bea.p13n.advisor.internal.CompoundAdvisletImpl.getAdvice(CompoundAdvisletImpl.java:88)
at com.bea.p13n.advisor.internal.AdvisorImpl.getAdvice(AdvisorImpl.java:74)
at com.bea.p13n.advisor.internal.EjbAdvisorImpl.getAdvice(EjbAdvisorImpl.java:62)
at com.bea.p13n.advisor.internal.EjbAdvisor_t707wa_EOImpl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
at com.bea.p13n.advisor.internal.EjbAdvisor_t707wa_EOImpl.getAdvice(Unknown Source)
at com.bea.p13n.servlets.jsp.taglib.DivTag.includeBody(DivTag.java:103)
at com.bea.p13n.servlets.jsp.taglib.DivTag.doStartTag(DivTag.java:169)
at jsp_servlet._portlets._footerlinks.__footerlinks._jspService(__footerlinks.java:247)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:60)
at org.apache.beehive.netui.pageflow.PageFlowPageFilter.continueChainNoWrapper(PageFlowPageFilter.java:455)
at org.apache.beehive.netui.pageflow.PageFlowPageFilter.runPage(PageFlowPageFilter.java:432)
at org.apache.beehive.netui.pageflow.PageFlowPageFilter.doFilter(PageFlowPageFilter.java:284)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:60)
at com.bea.netuix.servlets.filters.IncludeSecurityFilter.doFilter(IncludeSecurityFilter.java:103)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:60)
at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:524)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:444)
at com.bea.netuix.servlets.controls.content.JspContent.beginRender(JspContent.java:558)
at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:485)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:399)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:326)
at com.bea.netuix.nf.UIControl.render(UIControl.java:582)
at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:488)
at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:152)
at com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:62)
at jsp_servlet._framework._skeletons._ceoportal.__flowlayout._jspService(__flowlayout.java:139)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:183)
at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:526)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:444)
at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:148)
at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72)
at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65)
at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:399)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:326)
at com.bea.netuix.nf.UIControl.render(UIControl.java:582)
at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:488)
at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:152)
at com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:62)
at jsp_servlet._framework._skeletons._ceoportal.__gridlayout._jspService(__gridlayout.java:357)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:183)
at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:526)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:444)
at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:148)
at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72)
at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65)
at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:399)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
at com.bea.netuix.nf.Lifecycle.runOutbound(Lifecycle.java:208)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:162)
at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:465)
at com.bea.netuix.servlets.manager.UIServlet.processControlTree(UIServlet.java:373)
at com.bea.netuix.servlets.manager.PortalServlet.service(PortalServlet.java:993)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:60)
at com.bea.content.manager.servlets.ContentServletFilter.doFilter(ContentServletFilter.java:178)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:60)
at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:336)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:60)
at com.bea.portal.tools.servlet.http.HttpContextFilter.doFilter(HttpContextFilter.java:60)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:60)
at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:336)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:60)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3729)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3695)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2285)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2184)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1459)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)

The following document describes about how datasync data is deployed in various scenarios.
http://download.oracle.com/docs/cd/E13218_01/wlp/docs100/prodOps/preparing.html#wp1029497
Assuming you are making use of workshop for creating the user segment and deploying to a single server which is in development mode, I would recommend you check if you have hit any OOM issues on the server or not, and try restarting the server, and redeploying your app. Generally this should resolve the issue.
If the server to which you are deploying is running in production mode / deploying as an EAR then the above referred doc will guide you on the next steps.

What is the Relationship between Update Rule and Infopackage/Transfer Rules

Hello Experts,
can you help explain these scenarios to me:
What is the relationship between update rules and infopackges?
What is the relationship between transfer rules and infopackges?
What is the relationship between update rules and transfer rules?

Hello,
Info-packages trigger the data load into BW system from the source system. An info-package is created for a specific data source and info source combination.
1) When you trigger the info-package it sends an request to the source system to start the extraction process and this corresponds to the step "Data Request Received" in monitor under details tab. It is the first step.
2) Then the selections specified in the info-package are transferred to the source system to select the requested data from BW system. Then it is sent back to BW system.
3) Once it reach BW, it gets into the PSA and then it gets updated into the data target (depends on what settings are made in IP). No rules (Transfer rules / update rules) comes into picture when data is stored in PSA. Only the transfer structure is used to map the BW info-objects with the source system fields.
4) After data is stored into PSA, the update into the data targets begins. First the transfer rules are applied -> data then flows through the communication structure -> update rules are applied and finally the records gets updated into the data target.
The extraction flow is: -
Source System (DS) -> PSA -> Transfer Rules -> Communication Structure -> Update Rules -> Data target.
Info-package actually triggers the whole data flow in BW system.
Hope it gives you a clear picture.
Thx,
Soumya

ERMS Rule Modeler: Delete draft rules

Hello,
I have an urgent query on ERMS rule modeler.
Once a draft version is created, how can we delete it? I noticed that we can only delete the rules within the Draft rules node but not the node itself.
This way if you wish to edit the released rules again, it is not possible because it asks to release draft rules first (which you don't want).
Is there a way to delete the draft version or cancel the changes once draft version is created so that we can edit the released rule?
Any report or via rule modeler?
Best Regards,
Mohit

Hi Mohit,
hope I get your question right... but you have a node with released rules and one with draft...Just go to edit modus and delete the whole node...
Go to edit modus and select the node with Draft rules
Click on the Bucket and save and there are gone...
Hope it helps.
Regards,
Martin

Rule fragments in shortcut rules

I had a shortcut rule table that wasn't working, something along the lines of:
Shortcut rule*
the outcome of the transaction
"Outcome A" - AttributeX = 5
"Outcome B" - AttributeX = 6
"Outcome C" - AttributeY is true
"Outcome D" - AttributeZ is true
I thought the reason it may not be working was because I had conditions on multiple attributes within a single table. Thinking that rule fragments may be the answer, I split the rule into 3 fragments (each a shortcut rule, but still tables as I don't seem to be able to set the value of a text attribute any other way).
rule_property[fragment:1]
Shortcut rule*
the outcome of the transaction
"Outcome A" - AttributeX = 5
"Outcome B" - AttributeX = 6
rule_property[fragment:2]
Shortcut rule*
the outcome of the transaction
"Outcome C" - AttributeY is true
rule_property[fragment:3]
Shortcut rule*
the outcome of the transaction
"Outcome D" - AttributeZ is true
However, regardless of the values of attribues X, Y and Z, the rule always seems to set the value to Outcome A, any ideas? Is it permitted to use rule fragments in shortcut rules?

Going back to what I assume the original Word table looked like...
| the outcome of the transaction          |
| "Outcome A" | Attribute X = 5               |
| "Outcome B" | Attribute X = 6               |
| "Outcome C" | Attribute Y is true          |
| "Outcome D" | Attribute Z is true          |
| uncertain   | else                    |
-------------------------------------------------... you commented that "regardless of the values of attribues X, Y and Z, the rule always seems to set the value to Outcome A". I just tried the same rule table and it behaved exactly as I expected, so I think it's worth explaining how Word rule tables work.
Word rule tables start from the top of the table and work down until finding a table row for which the conditions are satisfied. If X = 5, then the first conditional row is satisfied and the conclusion is set to A. It doesn't matter what the values of Y and Z are, they will not impact the conclusion once X is set to 5.
If X is unknown, and Y=true, then the conclusion will be unknown. This is because it's not even going to get to the third conditional row until all conditional rows above have been disproven. Whereas if X=7 and Y=true, then the conclusion will be set to C, since the first and second conditional rows have been disproven, i.e. proven not to be 5 or 6. Make sense? :)
So when you were seeing the conclusion being set to A, regardless of the value of Y and Z, it must have been because X was set to 5 or 6. If there's a logic order to how you'd progress through the options, then just use that order in the rows of your rule table. Presumably you need to think thorough this logic anyway since you need to think about what's meant to happen if X=5 and Y=true? Should the conclusion be set to A or C? If it's the case that when Y=true, it trumps everything and the conclusion should be C, then just make that the first conditional line of your rule table.

TS1398 I only want my secured network wifi but keeps searching for others. Tried turning on an off wifi and on and off secured networks and ignore other networks, but keep coming back. Any suggestions.

I only want my secured network wifi but keeps searching for others. Tried turning on an off wifi and on and off secured networks and ignore other networks, but keep coming back. Any suggestions.

That's not the way wifi works.
You may see the other networks but you are not connected to them in any way.

[solved] /etc/udev/rules.d/10-network.rules ignored

Similar Messages

Maybe you are looking for