'프로그램 사용'에 해당되는 글 2342건

  1. 2025.07.23 zabbix docker 설치 1
  2. 2025.07.22 libreNMS on docker
  3. 2025.07.21 iptime snmp mib
  4. 2025.07.21 snmpbulkwalk
  5. 2025.07.21 libreNMS
  6. 2025.05.26 libreoffice calc 보이는 셀만 복사
  7. 2025.05.22 libfreenect2 VAAPI 버그? 2
  8. 2025.05.22 ros2 with kinect v2 시도... 3회차
  9. 2025.05.22 git master -> main branch
  10. 2025.05.22 ros2 with kinect v2 시도... 2회차
프로그램 사용/snmp2025. 7. 23. 11:39

설치를 하고 설정을 해보아도 역시 grafana 이런거 안쓰면 별루인가...

무난한건 Example 1 일 듯.

Example 1
The example demonstrates how to run Zabbix server with MySQL database support, Zabbix web interface based on the Nginx web server and Zabbix Java gateway.


Example 2
The example demonstrates how to run Zabbix server with PostgreSQL database support, Zabbix web interface based on the Nginx web server and SNMP trap feature.


Example 3
The example demonstrates how to run Zabbix server with MySQL database support, Zabbix web interface based on the Nginx web server and Zabbix Java gateway using podman on Red Hat 8.

[링크 : https://www.zabbix.com/documentation/current/en/manual/installation/containers]

[링크 : https://www.zabbix.com/documentation/current/en/manual/quickstart/login]

'프로그램 사용 > snmp' 카테고리의 다른 글

libreNMS FDB?  (0) 2025.07.28
win 10 snmp 서비스  (0) 2025.07.24
libreNMS on docker  (0) 2025.07.22
iptime snmp mib  (0) 2025.07.21
snmpbulkwalk  (0) 2025.07.21
Posted by 구차니
프로그램 사용/snmp2025. 7. 22. 11:37

아직 쓰는 법이 익숙하지 않아서인지 아니면 지원하지 않는 기능인지 몰라서 헤매는 중

처음 설치하고 장치를 추가하면 조금의 시간이 지나면 그래프들이 그려진다.

 

회사에 있는 두개 장비 iptime과 복합기를 추가하고

 

공유기는 아래와 같이 좀 심심한 정보들

 

복합기는 토너 관련 정보들이 추가되서 신기하다

 

 

[링크 : https://docs.librenms.org/Installation/Docker/]

'프로그램 사용 > snmp' 카테고리의 다른 글

win 10 snmp 서비스  (0) 2025.07.24
zabbix docker 설치  (1) 2025.07.23
iptime snmp mib  (0) 2025.07.21
snmpbulkwalk  (0) 2025.07.21
libreNMS  (0) 2025.07.21
Posted by 구차니
프로그램 사용/snmp2025. 7. 21. 11:42

공유기 페이지에서 ipTIME-Router-MIB 라고 되어있어서 다운로드 받았는데

[링크 : http://download.iptime.co.kr/download/snmp/IPTIME-ROUTER-MIB.zip]

 

 

뭐.. 되는게 없네?

$ snmpbulkwalk -v 2c -c test -m ALL 192.168.10.1

 

그 중에 iptime만 필터 걸어서 보는데 뭐여..

Cannot find module (SNMP-FRAMEWORK-MIB): At line 6 in /usr/share/snmp/mibs/IPTIME-ROUTER-MIB.txt
Cannot find module (SNMPv2-SMI): At line 8 in /usr/share/snmp/mibs/IPTIME-MIB.txt
Did not find 'enterprises' in module #-1 (/usr/share/snmp/mibs/IPTIME-MIB.txt)
Unlinked OID in IPTIME-MIB: ipTime ::= { enterprises 12874 }
Unlinked OID in IPTIME-MIB: ipTime ::= { enterprises 12874 }
Undefined identifier: enterprises near line 10 of /usr/share/snmp/mibs/IPTIME-MIB.txt
Cannot find module (SNMPv2-TC): At line 9 in /usr/share/snmp/mibs/IPTIME-ROUTER-MIB.txt
Cannot find module (INET-ADDRESS-MIB): At line 12 in /usr/share/snmp/mibs/IPTIME-ROUTER-MIB.txt
Did not find 'SnmpAdminString' in module #-1 (/usr/share/snmp/mibs/IPTIME-ROUTER-MIB.txt)
Did not find 'ipTime' in module IPTIME-MIB (/usr/share/snmp/mibs/IPTIME-ROUTER-MIB.txt)
Did not find 'ipTime' in module IPTIME-MIB (/usr/share/snmp/mibs/IPTIME-ROUTER-MIB.txt)
Did not find 'ipTime' in module IPTIME-MIB (/usr/share/snmp/mibs/IPTIME-ROUTER-MIB.txt)
Did not find 'DisplayString' in module #-1 (/usr/share/snmp/mibs/IPTIME-ROUTER-MIB.txt)
Did not find 'RowStatus' in module #-1 (/usr/share/snmp/mibs/IPTIME-ROUTER-MIB.txt)
Did not find 'StorageType' in module #-1 (/usr/share/snmp/mibs/IPTIME-ROUTER-MIB.txt)
Did not find 'PhysAddress' in module #-1 (/usr/share/snmp/mibs/IPTIME-ROUTER-MIB.txt)
Did not find 'TimeStamp' in module #-1 (/usr/share/snmp/mibs/IPTIME-ROUTER-MIB.txt)
Did not find 'InetAddressType' in module #-1 (/usr/share/snmp/mibs/IPTIME-ROUTER-MIB.txt)
Did not find 'InetAddress' in module #-1 (/usr/share/snmp/mibs/IPTIME-ROUTER-MIB.txt)
Unlinked OID in IPTIME-ROUTER-MIB: ipTimeRouter ::= { ipTime 1 }
Unlinked OID in IPTIME-ROUTER-MIB: ipTimeRouter ::= { ipTime 1 }
Unlinked OID in IPTIME-ROUTER-MIB: ipTimeRouter ::= { ipTime 1 }
Undefined identifier: ipTime near line 15 of /usr/share/snmp/mibs/IPTIME-ROUTER-MIB.txt
Undefined identifier: ipTime near line 15 of /usr/share/snmp/mibs/IPTIME-ROUTER-MIB.txt
Cannot adopt OID in IPTIME-ROUTER-MIB: ifaceEntry ::= { ifaceTable 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: ipTimeRouter ::= { ipTime 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: ipTimeRouter ::= { ipTime 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: ipTimeRouter ::= { ipTime 1 }
Cannot adopt OID in IPTIME-MIB: ipTimeRouter ::= { ipTime 1 }
Cannot adopt OID in IPTIME-MIB: ipTimeRouter ::= { ipTime 1 }
Cannot adopt OID in IPTIME-MIB: ipTimeRouter ::= { ipTime 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: essTable ::= { routerWireless 2 }
Cannot adopt OID in IPTIME-ROUTER-MIB: essNumber ::= { routerWireless 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: atIpAddress ::= { addressEntry 3 }
Cannot adopt OID in IPTIME-ROUTER-MIB: atPhysAddress ::= { addressEntry 2 }
Cannot adopt OID in IPTIME-ROUTER-MIB: atIfDescr ::= { addressEntry 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: routerTraps ::= { ipTimeRouter 9000 }
Cannot adopt OID in IPTIME-ROUTER-MIB: routerTraps ::= { ipTimeRouter 9000 }
Cannot adopt OID in IPTIME-ROUTER-MIB: routerSystem ::= { ipTimeRouter 5 }
Cannot adopt OID in IPTIME-ROUTER-MIB: routerSystem ::= { ipTimeRouter 5 }
Cannot adopt OID in IPTIME-ROUTER-MIB: routerWireless ::= { ipTimeRouter 4 }
Cannot adopt OID in IPTIME-ROUTER-MIB: routerWireless ::= { ipTimeRouter 4 }
Cannot adopt OID in IPTIME-ROUTER-MIB: routerAddressTbl ::= { ipTimeRouter 3 }
Cannot adopt OID in IPTIME-ROUTER-MIB: routerAddressTbl ::= { ipTimeRouter 3 }
Cannot adopt OID in IPTIME-ROUTER-MIB: routerInterface ::= { ipTimeRouter 2 }
Cannot adopt OID in IPTIME-ROUTER-MIB: routerInterface ::= { ipTimeRouter 2 }
Cannot adopt OID in IPTIME-ROUTER-MIB: routerInformation ::= { ipTimeRouter 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: routerInformation ::= { ipTimeRouter 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: ifaceStatus ::= { ifaceEntry 4 }
Cannot adopt OID in IPTIME-ROUTER-MIB: ifaceMode ::= { ifaceEntry 3 }
Cannot adopt OID in IPTIME-ROUTER-MIB: ifaceDescr ::= { ifaceEntry 2 }
Cannot adopt OID in IPTIME-ROUTER-MIB: ifaceIndex ::= { ifaceEntry 1 }
Cannot adopt OID in IPTIME-MIB: ipTime ::= { enterprises 12874 }
Cannot adopt OID in IPTIME-MIB: ipTime ::= { enterprises 12874 }
Cannot adopt OID in IPTIME-ROUTER-MIB: Reboot ::= { routerSystem 7 }
Cannot adopt OID in IPTIME-ROUTER-MIB: UpgradeStart ::= { routerSystem 6 }
Cannot adopt OID in IPTIME-ROUTER-MIB: RemoteAccessPort ::= { routerSystem 5 }
Cannot adopt OID in IPTIME-ROUTER-MIB: SecondayDNS ::= { routerSystem 4 }
Cannot adopt OID in IPTIME-ROUTER-MIB: PrimaryDNS ::= { routerSystem 3 }
Cannot adopt OID in IPTIME-ROUTER-MIB: WanMac ::= { routerSystem 2 }
Cannot adopt OID in IPTIME-ROUTER-MIB: LanMac ::= { routerSystem 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: Version ::= { routerInformation 3 }
Cannot adopt OID in IPTIME-ROUTER-MIB: Model ::= { routerInformation 2 }
Cannot adopt OID in IPTIME-ROUTER-MIB: Manufacturer ::= { routerInformation 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: addressTable ::= { routerAddressTbl 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: internetDiscon ::= { routerTraps 6 }
Cannot adopt OID in IPTIME-ROUTER-MIB: internetConn ::= { routerTraps 5 }
Cannot adopt OID in IPTIME-ROUTER-MIB: wanlinkDown ::= { routerTraps 4 }
Cannot adopt OID in IPTIME-ROUTER-MIB: wanlinkUp ::= { routerTraps 3 }
Cannot adopt OID in IPTIME-ROUTER-MIB: forceRebootOk ::= { routerTraps 2 }
Cannot adopt OID in IPTIME-ROUTER-MIB: rebootOk ::= { routerTraps 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: ifaceTable ::= { routerInterface 2 }
Cannot adopt OID in IPTIME-ROUTER-MIB: ifaceNumber ::= { routerInterface 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: essEntry ::= { essTable 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: addressEntry ::= { addressTable 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: essChannelInfo ::= { essEntry 10 }
Cannot adopt OID in IPTIME-ROUTER-MIB: ess8021xRadiusPort ::= { essEntry 9 }
Cannot adopt OID in IPTIME-ROUTER-MIB: ess8021xRadiusKey ::= { essEntry 8 }
Cannot adopt OID in IPTIME-ROUTER-MIB: ess8021xRadiusIPaddress ::= { essEntry 7 }
Cannot adopt OID in IPTIME-ROUTER-MIB: essSecurityKey ::= { essEntry 6 }
Cannot adopt OID in IPTIME-ROUTER-MIB: essSecuritySet ::= { essEntry 5 }
Cannot adopt OID in IPTIME-ROUTER-MIB: essMode ::= { essEntry 4 }
Cannot adopt OID in IPTIME-ROUTER-MIB: essSsidBroadcast ::= { essEntry 3 }
Cannot adopt OID in IPTIME-ROUTER-MIB: essSsid ::= { essEntry 2 }
Cannot adopt OID in IPTIME-ROUTER-MIB: essIndex ::= { essEntry 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: ifaceEntry ::= { ifaceTable 1 }
Cannot adopt OID in IPTIME-MIB: ipTimeRouter ::= { ipTime 1 }
Cannot adopt OID in IPTIME-MIB: ipTimeRouter ::= { ipTime 1 }
Cannot adopt OID in IPTIME-MIB: ipTimeRouter ::= { ipTime 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: ipTimeRouter ::= { ipTime 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: ipTimeRouter ::= { ipTime 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: ipTimeRouter ::= { ipTime 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: essNumber ::= { routerWireless 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: essTable ::= { routerWireless 2 }
Cannot adopt OID in IPTIME-ROUTER-MIB: atIfDescr ::= { addressEntry 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: atPhysAddress ::= { addressEntry 2 }
Cannot adopt OID in IPTIME-ROUTER-MIB: atIpAddress ::= { addressEntry 3 }
Cannot adopt OID in IPTIME-ROUTER-MIB: routerInformation ::= { ipTimeRouter 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: routerInformation ::= { ipTimeRouter 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: routerInterface ::= { ipTimeRouter 2 }
Cannot adopt OID in IPTIME-ROUTER-MIB: routerInterface ::= { ipTimeRouter 2 }
Cannot adopt OID in IPTIME-ROUTER-MIB: routerAddressTbl ::= { ipTimeRouter 3 }
Cannot adopt OID in IPTIME-ROUTER-MIB: routerAddressTbl ::= { ipTimeRouter 3 }
Cannot adopt OID in IPTIME-ROUTER-MIB: routerWireless ::= { ipTimeRouter 4 }
Cannot adopt OID in IPTIME-ROUTER-MIB: routerWireless ::= { ipTimeRouter 4 }
Cannot adopt OID in IPTIME-ROUTER-MIB: routerSystem ::= { ipTimeRouter 5 }
Cannot adopt OID in IPTIME-ROUTER-MIB: routerSystem ::= { ipTimeRouter 5 }
Cannot adopt OID in IPTIME-ROUTER-MIB: routerTraps ::= { ipTimeRouter 9000 }
Cannot adopt OID in IPTIME-ROUTER-MIB: routerTraps ::= { ipTimeRouter 9000 }
Cannot adopt OID in IPTIME-ROUTER-MIB: ifaceIndex ::= { ifaceEntry 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: ifaceDescr ::= { ifaceEntry 2 }
Cannot adopt OID in IPTIME-ROUTER-MIB: ifaceMode ::= { ifaceEntry 3 }
Cannot adopt OID in IPTIME-ROUTER-MIB: ifaceStatus ::= { ifaceEntry 4 }
Cannot adopt OID in IPTIME-MIB: ipTime ::= { enterprises 12874 }
Cannot adopt OID in IPTIME-MIB: ipTime ::= { enterprises 12874 }
Cannot adopt OID in IPTIME-ROUTER-MIB: LanMac ::= { routerSystem 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: WanMac ::= { routerSystem 2 }
Cannot adopt OID in IPTIME-ROUTER-MIB: PrimaryDNS ::= { routerSystem 3 }
Cannot adopt OID in IPTIME-ROUTER-MIB: SecondayDNS ::= { routerSystem 4 }
Cannot adopt OID in IPTIME-ROUTER-MIB: RemoteAccessPort ::= { routerSystem 5 }
Cannot adopt OID in IPTIME-ROUTER-MIB: UpgradeStart ::= { routerSystem 6 }
Cannot adopt OID in IPTIME-ROUTER-MIB: Reboot ::= { routerSystem 7 }
Cannot adopt OID in IPTIME-ROUTER-MIB: Manufacturer ::= { routerInformation 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: Model ::= { routerInformation 2 }
Cannot adopt OID in IPTIME-ROUTER-MIB: Version ::= { routerInformation 3 }
Cannot adopt OID in IPTIME-ROUTER-MIB: addressTable ::= { routerAddressTbl 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: rebootOk ::= { routerTraps 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: forceRebootOk ::= { routerTraps 2 }
Cannot adopt OID in IPTIME-ROUTER-MIB: wanlinkUp ::= { routerTraps 3 }
Cannot adopt OID in IPTIME-ROUTER-MIB: wanlinkDown ::= { routerTraps 4 }
Cannot adopt OID in IPTIME-ROUTER-MIB: internetConn ::= { routerTraps 5 }
Cannot adopt OID in IPTIME-ROUTER-MIB: internetDiscon ::= { routerTraps 6 }
Cannot adopt OID in IPTIME-ROUTER-MIB: ifaceNumber ::= { routerInterface 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: ifaceTable ::= { routerInterface 2 }
Cannot adopt OID in IPTIME-ROUTER-MIB: essEntry ::= { essTable 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: addressEntry ::= { addressTable 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: essIndex ::= { essEntry 1 }
Cannot adopt OID in IPTIME-ROUTER-MIB: essSsid ::= { essEntry 2 }
Cannot adopt OID in IPTIME-ROUTER-MIB: essSsidBroadcast ::= { essEntry 3 }
Cannot adopt OID in IPTIME-ROUTER-MIB: essMode ::= { essEntry 4 }
Cannot adopt OID in IPTIME-ROUTER-MIB: essSecuritySet ::= { essEntry 5 }
Cannot adopt OID in IPTIME-ROUTER-MIB: essSecurityKey ::= { essEntry 6 }
Cannot adopt OID in IPTIME-ROUTER-MIB: ess8021xRadiusIPaddress ::= { essEntry 7 }
Cannot adopt OID in IPTIME-ROUTER-MIB: ess8021xRadiusKey ::= { essEntry 8 }
Cannot adopt OID in IPTIME-ROUTER-MIB: ess8021xRadiusPort ::= { essEntry 9 }
Cannot adopt OID in IPTIME-ROUTER-MIB: essChannelInfo ::= { essEntry 10 }

 

전부 받고 -m ALL 옵션을 주면 좀 먼가 바뀌긴 한다.

[링크 : https://github.com/net-snmp/net-snmp/tree/master/mibs]

'프로그램 사용 > snmp' 카테고리의 다른 글

zabbix docker 설치  (1) 2025.07.23
libreNMS on docker  (0) 2025.07.22
snmpbulkwalk  (0) 2025.07.21
libreNMS  (0) 2025.07.21
snmp 클라이언트 - snmpwalk, snmpget  (0) 2024.05.17
Posted by 구차니
프로그램 사용/snmp2025. 7. 21. 11:17

snmpwalk 보다 snmpbulkwalk가 빠르게 작동하긴 한다.

기능이나 옵션은 거의 동일한 것 같다.

 

$ snmpwalk -v 2c  -c test 192.168.10.1 $ time snmpbulkwalk -v 2c -c test192.168.10.1
real 0m5.757s
user 0m0.203s
sys 0m0.249s
real 0m1.691s
user 0m0.035s
sys 0m0.026s

[링크 : https://mabb.tistory.com/590]

[링크 : https://manpages.ubuntu.com/manpages/lunar/man1/snmpbulkwalk.1.html]

 

+

MIB 파일 관련

[링크 : https://atin.tistory.com/220]

[링크 : https://haewon83.tistory.com/m/76]

 

export MIBS=ALL

Put STRANGE-NEW-MIB.txt in the directory where all your other MIBs are stored (possibly /usr/share/snmp/mibs , but it may vary with distro, mine is Fedora 14), then do

snmpwalk -v 1 -c public -m +STRANGE-NEW-MIB 1.2.3.4

[링크 : https://serverfault.com/questions/220576/how-to-use-a-mib-file]

 

snmp agent, snmptranslate

[링크 : https://whitewing4139.tistory.com/168]

'프로그램 사용 > snmp' 카테고리의 다른 글

libreNMS on docker  (0) 2025.07.22
iptime snmp mib  (0) 2025.07.21
libreNMS  (0) 2025.07.21
snmp 클라이언트 - snmpwalk, snmpget  (0) 2024.05.17
WinXP에서 SNMP 설치하기  (0) 2011.11.21
Posted by 구차니
프로그램 사용/snmp2025. 7. 21. 10:45

snmp 모니터링 해보려고 하는데 GUI 무료 툴을 찾는 중 하나 발견

[링크 : https://www.librenms.org/]

 

어우.. 패키지 요구하는게 장난 아니네

apt install acl curl fping git graphviz imagemagick mariadb-client mariadb-server mtr-tiny nginx-full nmap php-cli php-curl php-fpm php-gd php-gmp php-json php-mbstring php-mysql php-snmp php-xml php-zip rrdtool snmp snmpd unzip python3-command-runner python3-pymysql python3-dotenv python3-redis python3-setuptools python3-psutil python3-systemd python3-pip whois traceroute

[링크 : https://docs.librenms.org/Installation/Install-LibreNMS/]

[링크 : https://kimsoy-security.tistory.com/87]

'프로그램 사용 > snmp' 카테고리의 다른 글

iptime snmp mib  (0) 2025.07.21
snmpbulkwalk  (0) 2025.07.21
snmp 클라이언트 - snmpwalk, snmpget  (0) 2024.05.17
WinXP에서 SNMP 설치하기  (0) 2011.11.21
snmp - ubuntu  (0) 2011.11.21
Posted by 구차니
Posted by 구차니
프로그램 사용/kinect2025. 5. 22. 23:51

intel 7세대 노트북에서

별 옵션 주지 않고 cmake 하니까 아래와 같이 설정이 된다.

2세대 에서는 OpenCL yes, VAAPI no 였다.

-- Using in-tree freenect2 target
-- Feature list:
--   CUDA    no
--   CXX11    disabled
--   Examples    yes
--   OpenCL    no
--   OpenGL    yes
--   OpenNI2    yes
--   TegraJPEG    no
--   Threading    tinythread
--   TurboJPEG    yes
--   VAAPI    yes
--   VideoToolbox    no (Apple only)
--   streamer_recorder    disabled
-- Configuring done (0.1s)
-- Generating done (0.0s)

 

그래서 떴던거 같아서 다시 실행해보니 ir 과 depth는 정상이고 rgb의 폭이 이상해서

3d로 재구성된 녀석도 이상하게 나온다.

$ ./Protonect 
Version: 0.2.0
Environment variables: LOGFILE=<protonect.log>
Usage: ./Protonect [-gpu=<id>] [gl | cl | clkde | cuda | cudakde | cpu] [<device serial>]
        [-noviewer] [-norgb | -nodepth] [-help] [-version]
        [-frames <number of frames to process>]
To pause and unpause: pkill -USR1 Protonect
[Info] [Freenect2Impl] enumerating devices...
[Info] [Freenect2Impl] 9 usb devices connected
[Info] [Freenect2Impl] found valid Kinect v2 @2:11 with serial 501441643042
[Info] [Freenect2Impl] found 1 devices
libva info: VA-API version 1.20.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_20
libva info: va_openDriver() returns 0
[Info] [VaapiRgbPacketProcessorImpl] driver: Intel iHD driver for Intel(R) Gen Graphics - 24.1.0 ()
[Info] [Freenect2DeviceImpl] opening...
[Info] [Freenect2DeviceImpl] transfer pool sizes rgb: 20*16384 ir: 60*8*33792
[Info] [Freenect2DeviceImpl] opened
[Info] [Freenect2DeviceImpl] starting...
[Debug] [Freenect2DeviceImpl] status 0x090000: 9729
[Debug] [Freenect2DeviceImpl] status 0x090000: 9731
[Info] [Freenect2DeviceImpl] submitting rgb transfers...
[Info] [Freenect2DeviceImpl] submitting depth transfers...
[Info] [Freenect2DeviceImpl] started

 

그래서 VAAPI를 끄고 빌드해서 실행해보니

$ cmake .. -DENABLE_VAAPI=OFF
-- Using in-tree freenect2 target
-- Feature list:
--   CUDA    no
--   CXX11    disabled
--   Examples    yes
--   OpenCL    no
--   OpenGL    yes
--   OpenNI2    yes
--   TegraJPEG    no
--   Threading    tinythread
--   TurboJPEG    yes
--   VAAPI    disabled
--   VideoToolbox    no (Apple only)
--   streamer_recorder    disabled
-- Configuring done (0.1s)
-- Generating done (0.0s)

 

영상은 정상적으로 보이는데, transfer pool size가 달라지진 않네.. 머지?

$ ./Protonect 
Version: 0.2.0
Environment variables: LOGFILE=<protonect.log>
Usage: ./Protonect [-gpu=<id>] [gl | cl | clkde | cuda | cudakde | cpu] [<device serial>]
        [-noviewer] [-norgb | -nodepth] [-help] [-version]
        [-frames <number of frames to process>]
To pause and unpause: pkill -USR1 Protonect
[Info] [Freenect2Impl] enumerating devices...
[Info] [Freenect2Impl] 9 usb devices connected
[Info] [Freenect2Impl] found valid Kinect v2 @2:11 with serial 501441643042
[Info] [Freenect2Impl] found 1 devices
[Info] [Freenect2DeviceImpl] opening...
[Info] [Freenect2DeviceImpl] transfer pool sizes rgb: 20*16384 ir: 60*8*33792
[Info] [Freenect2DeviceImpl] opened
[Info] [Freenect2DeviceImpl] starting...
[Debug] [Freenect2DeviceImpl] status 0x090000: 9729
[Debug] [Freenect2DeviceImpl] status 0x090000: 9731
[Info] [Freenect2DeviceImpl] submitting rgb transfers...
[Info] [Freenect2DeviceImpl] submitting depth transfers...
[Debug] [DepthPacketStreamParser] not all subsequences received 0
[Info] [Freenect2DeviceImpl] started

 

 

Posted by 구차니
프로그램 사용/ros2025. 5. 22. 23:20

다른 사용자의 것과는 다르게 알아서 시리얼을 확인하고 그냥 선택한다.

그때는 물려볼게 없어서 안 죽었나 싶긴한데.

 

요건 wayland 에서 한 거(우분투 기본 값이니)

$ ros2 launch kinect2_bridge kinect2_bridge_launch.yaml
[INFO] [launch]: All log files can be found below /home/minimonk/.ros/log/2025-05-22-23-16-49-714642-minimonk-900X3N-4099
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [kinect2_bridge_node-1]: process started with pid [4102]
[INFO] [point_cloud_xyzrgb_node-2]: process started with pid [4103]
[kinect2_bridge_node-1] [INFO] [1747923410.103073698] [kinect2_bridge_node]: parameter:
[kinect2_bridge_node-1]         base_name: kinect2
[kinect2_bridge_node-1]            sensor: default
[kinect2_bridge_node-1]         fps_limit: 30
[kinect2_bridge_node-1]        calib_path: /home/minimonk/src/kinect2_ros2/kinect2_bridge/data/
[kinect2_bridge_node-1]           use_png: false
[kinect2_bridge_node-1]      jpeg_quality: 90
[kinect2_bridge_node-1]         png_level: 1
[kinect2_bridge_node-1]      depth_method: default
[kinect2_bridge_node-1]      depth_device: -1
[kinect2_bridge_node-1]        reg_method: default
[kinect2_bridge_node-1]        reg_device: -1
[kinect2_bridge_node-1]         max_depth: 12
[kinect2_bridge_node-1]         min_depth: 0.1
[kinect2_bridge_node-1]        queue_size: 5
[kinect2_bridge_node-1]  bilateral_filter: true
[kinect2_bridge_node-1] edge_aware_filter: true
[kinect2_bridge_node-1]        publish_tf: true
[kinect2_bridge_node-1]      base_name_tf: kinect2
[kinect2_bridge_node-1]    worker_threads: 4
[kinect2_bridge_node-1] libva info: VA-API version 1.20.0
[kinect2_bridge_node-1] libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
[kinect2_bridge_node-1] libva info: Found init function __vaDriverInit_1_20
[kinect2_bridge_node-1] libva info: va_openDriver() returns 0
[kinect2_bridge_node-1] [INFO] [1747923410.268596885] [kinect2_bridge_node]: Kinect2 devices found: 
[kinect2_bridge_node-1] [INFO] [1747923410.268646704] [kinect2_bridge_node]:   0: 501441643042 (selected)
[kinect2_bridge_node-1] [INFO] [1747923410.353586296] [kinect2_bridge_node]: starting kinect2
[kinect2_bridge_node-1] [INFO] [1747923410.702466968] [kinect2_bridge_node]: device serial: 501441643042
[kinect2_bridge_node-1] [INFO] [1747923410.702527385] [kinect2_bridge_node]: device firmware: 4.0.3911.0
[kinect2_bridge_node-1] [WARN] [1747923410.943823711] [kinect2_bridge_node]: using sensor defaults for color intrinsic parameters.
[kinect2_bridge_node-1] [WARN] [1747923410.943872088] [kinect2_bridge_node]: using sensor defaults for ir intrinsic parameters.
[kinect2_bridge_node-1] [WARN] [1747923410.943884124] [kinect2_bridge_node]: using defaults for rotation and translation.
[kinect2_bridge_node-1] [WARN] [1747923410.943893248] [kinect2_bridge_node]: using defaults for depth shift.
[kinect2_bridge_node-1] [INFO] [1747923410.957002369] [kinect2_bridge_node]: Using CPU registration method!
[kinect2_bridge_node-1] [INFO] [1747923410.957063941] [kinect2_bridge_node]: Using CPU registration method!
[kinect2_bridge_node-1] [INFO] [1747923410.989757825] [kinect2_bridge_node]: waiting for clients to connect
[kinect2_bridge_node-1] [INFO] [1747923435.975438490] [kinect2_bridge_node]: client connected. starting device...
[kinect2_bridge_node-1] X Error of failed request:  BadAccess (attempt to access private resource denied)
[kinect2_bridge_node-1]   Major opcode of failed request:  149 (GLX)
[kinect2_bridge_node-1]   Minor opcode of failed request:  5 (X_GLXMakeCurrent)
[kinect2_bridge_node-1]   Serial number of failed request:  186
[kinect2_bridge_node-1]   Current serial number in output stream:  186
[kinect2_bridge_node-1] terminate called after throwing an instance of 'rclcpp::exceptions::RCLError'
[kinect2_bridge_node-1]   what():  failed to publish message: cannot publish data, at ./src/rmw_publish.cpp:66, at ./src/rcl/publisher.c:284
[ERROR] [kinect2_bridge_node-1]: process has died [pid 4102, exit code -6, cmd '/home/minimonk/src/kinect2_ros2/install/kinect2_bridge/lib/kinect2_bridge/kinect2_bridge_node --ros-args -r __node:=kinect2_bridge_node --params-file /tmp/launch_params_iwksxu1_ --params-file /tmp/launch_params_1kuvaz_1 --params-file /tmp/launch_params_01a053mv --params-file /tmp/launch_params_zdcsdjyg --params-file /tmp/launch_params_yuzabhyr --params-file /tmp/launch_params_19tmdd6j --params-file /tmp/launch_params_hba7y_ha --params-file /tmp/launch_params_cz5d_5a0 --params-file /tmp/launch_params_zdnm6_6f --params-file /tmp/launch_params_0c2pkcpz --params-file /tmp/launch_params_z9p0frw3 --params-file /tmp/launch_params_93jygjmd --params-file /tmp/launch_params_gbcl6pwo --params-file /tmp/launch_params_h2ixukh_'].

 

X 에러가 나서 혹시나 해 로그아웃했다가 wayland에서 x.org로 변경해서 했는데 흐음..

안되는건 여전하네. 모르겠다! ㅠㅠ

[kinect2_bridge_node-1] X Error of failed request:  BadAccess (attempt to access private resource denied)
[kinect2_bridge_node-1]   Major opcode of failed request:  152 (GLX)
[kinect2_bridge_node-1]   Minor opcode of failed request:  5 (X_GLXMakeCurrent)
[kinect2_bridge_node-1]   Serial number of failed request:  189
[kinect2_bridge_node-1]   Current serial number in output stream:  189
[kinect2_bridge_node-1] terminate called after throwing an instance of 'std::system_error'
[kinect2_bridge_node-1]   what():  Invalid argument
[ERROR] [kinect2_bridge_node-1]: process has died [pid 7073, exit code -6, cmd '/home/minimonk/src/kinect2_ros2/install/kinect2_bridge/lib/kinect2_bridge/kinect2_bridge_node --ros-args -r __node:=kinect2_bridge_node --params-file /tmp/launch_params_y5bvhzyw --params-file /tmp/launch_params_gxirdqdy --params-file /tmp/launch_params_hp4gbet8 --params-file /tmp/launch_params_08p1acor --params-file /tmp/launch_params_lmxr_tz6 --params-file /tmp/launch_params_t_ro1l1e --params-file /tmp/launch_params_lijjyb5p --params-file /tmp/launch_params_kyd4zb0u --params-file /tmp/launch_params_4apk49ym --params-file /tmp/launch_params_01ocg_zs --params-file /tmp/launch_params_bz6p08h0 --params-file /tmp/launch_params_htcp1tsf --params-file /tmp/launch_params_7qjvyjg0 --params-file /tmp/launch_params_nqmk926s'].
^C[WARNING] [launch]: user interrupted with ctrl-c (SIGINT)
[point_cloud_xyzrgb_node-2] [INFO] [1747923700.776770005] [rclcpp]: signal_handler(signum=2)
[INFO] [point_cloud_xyzrgb_node-2]: process has finished cleanly [pid 7074]

 

흐음.. --params-file이 많은걸 제외하면 별 특별한건 없어 보이는데..

[pid 7073, 
exit code -6, 
cmd '/home/minimonk/src/kinect2_ros2/install/kinect2_bridge/lib/kinect2_bridge/kinect2_bridge_node 
--ros-args 
-r __node:=kinect2_bridge_node 
--params-file /tmp/launch_params_y5bvhzyw 
--params-file /tmp/launch_params_gxirdqdy 
--params-file /tmp/launch_params_hp4gbet8 
--params-file /tmp/launch_params_08p1acor 
--params-file /tmp/launch_params_lmxr_tz6 
--params-file /tmp/launch_params_t_ro1l1e 
--params-file /tmp/launch_params_lijjyb5p 
--params-file /tmp/launch_params_kyd4zb0u 
--params-file /tmp/launch_params_4apk49ym 
--params-file /tmp/launch_params_01ocg_zs 
--params-file /tmp/launch_params_bz6p08h0 
--params-file /tmp/launch_params_htcp1tsf 
--params-file /tmp/launch_params_7qjvyjg0 
--params-file /tmp/launch_params_nqmk926s'].

 

혹시나 해서 VAAPI를 쓴 libfreenect2의 문제인가 해서 빌드도 해서 바꾸어 봤는데 차이가 없다

머가 문제일까...

'프로그램 사용 > ros' 카테고리의 다른 글

ros2 with kinect v2 시도... 2회차  (0) 2025.05.22
ros2 with kinect v2 일단 실패  (0) 2025.05.21
ros2 uses concol  (0) 2025.05.20
ros 2 install on ubuntu 24.04, rviz  (2) 2025.05.17
ros...?  (0) 2025.04.08
Posted by 구차니

아놔... 어떻게 보면 그 쪽에서는 중요할지도 모르지만

컴퓨터 쪽 까지도 PC가 침범하게 될 줄이야.. -_-

 

[링크 : https://fabric0de.tistory.com/5]

[링크 : https://castellan.tistory.com/79]

'프로그램 사용 > Version Control' 카테고리의 다른 글

git local branch, merge master  (0) 2025.01.16
git switch  (0) 2025.01.16
git stash drop , clear  (0) 2024.09.19
git submodule ... 2?  (0) 2024.06.19
git diff --staged  (0) 2022.09.05
Posted by 구차니
프로그램 사용/ros2025. 5. 22. 00:13

다시 제대로 된(?) 녀석을 받고

[링크 : https://github.com/krepa098/kinect2_ros2]

어떻게 설치해서 빌드하는데

$ colcon build

 

kinect2_calibration에서 에러가 발생한다.

Starting >>> kinect2_calibration
--- stderr: kinect2_calibration                              
/home/minimonk/src/kinect2_ros2/kinect2_calibration/src/kinect2_calibration.cpp:37:10: fatal error: cv_bridge/cv_bridge.h: No such file or directory
   37 | #include "cv_bridge/cv_bridge.h"
      |          ^~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.

 

이리저리 찾아보다가 안되서 cv_bridge로 검색하니 include에 있는데.. 어? h가 아니라 hpp?

/opt/ros/jazzy/include/cv_bridge/cv_bridge$ ls -al
total 52
drwxr-xr-x 2 root root  4096 May 17 22:02 .
drwxr-xr-x 3 root root  4096 May 17 22:02 ..
-rw-r--r-- 1 root root  1079 Apr 30 09:03 cv_bridge_export.h
-rw-r--r-- 1 root root 12336 Jun 25  2024 cv_bridge.hpp
-rw-r--r-- 1 root root  9541 Jun 25  2024 cv_mat_sensor_msgs_image_type_adapter.hpp
-rw-r--r-- 1 root root  4160 Jun 25  2024 rgb_colors.hpp
-rw-r--r-- 1 root root  1814 Jun 25  2024 visibility_control.h

 

그래서 cv_bridge.h를 cv_bridge.hpp 로 바꾸어주고

$ git diff
diff --git a/kinect2_calibration/src/kinect2_calibration.cpp b/kinect2_calibration/src/kinect2_calibration.cpp
index 8e90a54..f4ce85c 100644
--- a/kinect2_calibration/src/kinect2_calibration.cpp
+++ b/kinect2_calibration/src/kinect2_calibration.cpp
@@ -34,7 +34,7 @@
 #include "sensor_msgs/msg/camera_info.hpp"
 #include "sensor_msgs/msg/image.hpp"
 
-#include "cv_bridge/cv_bridge.h"
+#include "cv_bridge/cv_bridge.hpp"
 
 #include "image_transport/image_transport.hpp"
 #include "image_transport/subscriber_filter.hpp"

 

빌드하니 성공!

$ colcon build
Starting >>> kinect2_registration
Finished <<< kinect2_registration [0.17s]                
Starting >>> kinect2_bridge
Finished <<< kinect2_bridge [0.15s]                  
Starting >>> kinect2_calibration
--- stderr: kinect2_calibration                                
/home/minimonk/src/kinect2_ros2/kinect2_calibration/src/kinect2_calibration.cpp:195: warning: ignoring ‘#pragma omp parallel’ [-Wunknown-pragmas]
  195 | #pragma omp parallel for
      | 
/home/minimonk/src/kinect2_ros2/kinect2_calibration/src/kinect2_calibration.cpp:658: warning: ignoring ‘#pragma omp parallel’ [-Wunknown-pragmas]
  658 | #pragma omp parallel for
      | 
/home/minimonk/src/kinect2_ros2/kinect2_calibration/src/kinect2_calibration.cpp:663: warning: ignoring ‘#pragma omp critical’ [-Wunknown-pragmas]
  663 | #pragma omp critical
      | 
/home/minimonk/src/kinect2_ros2/kinect2_calibration/src/kinect2_calibration.cpp:669: warning: ignoring ‘#pragma omp critical’ [-Wunknown-pragmas]
  669 | #pragma omp critical
      | 
/home/minimonk/src/kinect2_ros2/kinect2_calibration/src/kinect2_calibration.cpp:1162: warning: ignoring ‘#pragma omp parallel’ [-Wunknown-pragmas]
 1162 | #pragma omp parallel for
      | 
/home/minimonk/src/kinect2_ros2/kinect2_calibration/src/kinect2_calibration.cpp:1167: warning: ignoring ‘#pragma omp critical’ [-Wunknown-pragmas]
 1167 | #pragma omp critical
      | 
/home/minimonk/src/kinect2_ros2/kinect2_calibration/src/kinect2_calibration.cpp:1173: warning: ignoring ‘#pragma omp critical’ [-Wunknown-pragmas]
 1173 | #pragma omp critical
      | 
---
Finished <<< kinect2_calibration [12.1s]

Summary: 3 packages finished [12.5s]
  1 package had stderr output: kinect2_calibration

[링크 : https://docs.ros.org/en/jade/api/cv_bridge/html/c++/cv__bridge_8h_source.html]

    [링크 : https://docs.ros.org/en/jade/api/cv_bridge/html/c++/cv__bridge_8h.html]

 

그래서 뭔가를 실행하려고 하니 에러가 나서

~/src/kinect2_ros2/install$ source setup.bash
~/src/kinect2_ros2/install$ ros2 launch kinect2_bridge rtabmap.launch.py

 

패키지 잔뜩 깔아주니

$ sudo apt-get install ros-jazzy-rtabmap-odom
$ sudo apt-get install ros-jazzy-rtabmap-slam
$ sudo apt-get install ros-jazzy-rtabmap-viz

 

실행에 성공. 키넥트는 나중에 붙여서 slam 되나 봐야겠다.

---

 

이것저것 해보는데 되는게 없다.

ament_target_dependencies(${PROJECT_NAME} cv_bridge)

[링크 : https://www.reddit.com/r/ROS/comments/1f8bupf/cv_bridgeh_not_found_ros2/]

 

Something like this usually works for me:

ament_target_dependencies(synchronize_wo cv_bridge)
When using ament_target_dependencies you should not have to explicitly list the include and library files. Also not when you use target_link_libraries(synchronize_wo cv_bridge::cv_bridge)

[링크 : https://robotics.stackexchange.com/questions/112861/cv-bridge-h-not-found-ros2]

 

sudo apt-get install ros-dashing-cv-bridge

[링크 : https://answers.ros.org/question/308043/]

 

sudo apt-get install ros-kinetic-cv-bridge

[링크 : https://docs.ros.org/en/rolling/Releases/Release-Rolling-Ridley.html]

'프로그램 사용 > ros' 카테고리의 다른 글

ros2 with kinect v2 시도... 3회차  (0) 2025.05.22
ros2 with kinect v2 일단 실패  (0) 2025.05.21
ros2 uses concol  (0) 2025.05.20
ros 2 install on ubuntu 24.04, rviz  (2) 2025.05.17
ros...?  (0) 2025.04.08
Posted by 구차니