Skip to content

Fix a bug which caused SAI use unintialized log levels#193

Merged
lguohan merged 1 commit intosonic-net:masterfrom
pavel-shirshov:pavelsh/fix_logging
Apr 9, 2018
Merged

Fix a bug which caused SAI use unintialized log levels#193
lguohan merged 1 commit intosonic-net:masterfrom
pavel-shirshov:pavelsh/fix_logging

Conversation

@pavel-shirshov
Copy link
Contributor

@pavel-shirshov pavel-shirshov commented Apr 5, 2018

Fix a bug introduced by #186
Without the patch you can see following output. The SAI subsystem log levels weren't initialized:

ERR syncd: :- get_enum_value_from_name: not found SAI_API_SWITCH:SAI_API_SWITCH
ERR syncd: :- get_enum_value_from_name: not found SAI_API_PORT:SAI_API_PORT
ERR syncd: :- get_enum_value_from_name: not found SAI_API_FDB:SAI_API_FDB
ERR syncd: :- get_enum_value_from_name: not found SAI_API_VLAN:SAI_API_VLAN
ERR syncd: :- get_enum_value_from_name: not found SAI_API_VIRTUAL_ROUTER:SAI_API_VIRTUAL_ROUTER
ERR syncd: :- get_enum_value_from_name: not found SAI_API_ROUTE:SAI_API_ROUTE
ERR syncd: :- get_enum_value_from_name: not found SAI_API_NEXT_HOP:SAI_API_NEXT_HOP
ERR syncd: :- get_enum_value_from_name: not found SAI_API_NEXT_HOP_GROUP:SAI_API_NEXT_HOP_GROUP
ERR syncd: :- get_enum_value_from_name: not found SAI_API_ROUTER_INTERFACE:SAI_API_ROUTER_INTERFACE
ERR syncd: :- get_enum_value_from_name: not found SAI_API_NEIGHBOR:SAI_API_NEIGHBOR
ERR syncd: :- get_enum_value_from_name: not found SAI_API_ACL:SAI_API_ACL
ERR syncd: :- get_enum_value_from_name: not found SAI_API_HOSTIF:SAI_API_HOSTIF
ERR syncd: :- get_enum_value_from_name: not found SAI_API_MIRROR:SAI_API_MIRROR
ERR syncd: :- get_enum_value_from_name: not found SAI_API_SAMPLEPACKET:SAI_API_SAMPLEPACKET
ERR syncd: :- get_enum_value_from_name: not found SAI_API_STP:SAI_API_STP
ERR syncd: :- get_enum_value_from_name: not found SAI_API_LAG:SAI_API_LAG
ERR syncd: :- get_enum_value_from_name: not found SAI_API_POLICER:SAI_API_POLICER
ERR syncd: :- get_enum_value_from_name: not found SAI_API_WRED:SAI_API_WRED
ERR syncd: :- get_enum_value_from_name: not found SAI_API_QOS_MAP:SAI_API_QOS_MAP
ERR syncd: :- get_enum_value_from_name: not found SAI_API_QUEUE:SAI_API_QUEUE
ERR syncd: :- get_enum_value_from_name: not found SAI_API_SCHEDULER:SAI_API_SCHEDULER
ERR syncd: :- get_enum_value_from_name: not found SAI_API_SCHEDULER_GROUP:SAI_API_SCHEDULER_GROUP
ERR syncd: :- get_enum_value_from_name: not found SAI_API_BUFFER:SAI_API_BUFFER
ERR syncd: :- get_enum_value_from_name: not found SAI_API_HASH:SAI_API_HASH
ERR syncd: :- get_enum_value_from_name: not found SAI_API_UDF:SAI_API_UDF
ERR syncd: :- get_enum_value_from_name: not found SAI_API_TUNNEL:SAI_API_TUNNEL
ERR syncd: :- get_enum_value_from_name: not found SAI_API_L2MC:SAI_API_L2MC
ERR syncd: :- get_enum_value_from_name: not found SAI_API_IPMC:SAI_API_IPMC
ERR syncd: :- get_enum_value_from_name: not found SAI_API_RPF_GROUP:SAI_API_RPF_GROUP
ERR syncd: :- get_enum_value_from_name: not found SAI_API_L2MC_GROUP:SAI_API_L2MC_GROUP
ERR syncd: :- get_enum_value_from_name: not found SAI_API_IPMC_GROUP:SAI_API_IPMC_GROUP
ERR syncd: :- get_enum_value_from_name: not found SAI_API_MCAST_FDB:SAI_API_MCAST_FDB
ERR syncd: :- get_enum_value_from_name: not found SAI_API_BRIDGE:SAI_API_BRIDGE
ERR syncd: :- get_enum_value_from_name: not found SAI_API_TAM:SAI_API_TAM
ERR syncd: :- get_enum_value_from_name: not found SAI_API_SEGMENTROUTE:SAI_API_SEGMENTROUTE
ERR syncd: :- get_enum_value_from_name: not found SAI_API_MPLS:SAI_API_MPLS
ERR syncd: :- get_enum_value_from_name: not found SAI_API_UBURST:SAI_API_UBURST

@pavel-shirshov pavel-shirshov requested a review from lguohan April 5, 2018 22:18
@pavel-shirshov pavel-shirshov self-assigned this Apr 5, 2018
@lguohan lguohan merged commit e10a745 into sonic-net:master Apr 9, 2018
@pavel-shirshov pavel-shirshov deleted the pavelsh/fix_logging branch April 10, 2018 01:07
prgeor pushed a commit to prgeor/sonic-swss-common that referenced this pull request Feb 27, 2025
…rn (sonic-net#193)

Remove EEPROM cache file and use DB instead

1. Use visitor pattern accessing EEPROM data
2. Provide utility functions to access redis data base
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants