I've exhausted my search on trying to resolve this problem. I can't seem to get the example GATT server running in BlueZ 5.27. I'm running a Linux VM (kernel = 3.16) connected to a Broadcom BCM20702A0 Bluetooth 4.0 USB dongle. I can run hciconfig, hcitool, and gatttool with the associated commands and these work properly. I start advertising using,
sudo hciconfig hci0 leadv
However, when I try to run a BLe GATT server using,
bluetoothd -d -n
I get the following output:
bluetoothd[8075]: Bluetooth daemon 5.27
bluetoothd[8075]: src/gatt.c:gatt_init() Starting GATT server
bluetoothd[8075]: src/adapter.c:adapter_init() sending read version command
bluetoothd[8075]: Starting SDP server
bluetoothd[8075]: src/sdpd-service.c:register_device_id() Adding device id record for 0002:1d6b:0246:051b
bluetoothd[8075]: src/plugin.c:plugin_init() Loading builtin plugins
bluetoothd[8075]: src/plugin.c:add_plugin() Loading hostname plugin
bluetoothd[8075]: src/plugin.c:add_plugin() Loading wiimote plugin
bluetoothd[8075]: src/plugin.c:add_plugin() Loading autopair plugin
bluetoothd[8075]: src/plugin.c:add_plugin() Loading policy plugin
bluetoothd[8075]: src/plugin.c:add_plugin() Loading gatt_example plugin
bluetoothd[8075]: src/plugin.c:add_plugin() Loading neard plugin
bluetoothd[8075]: src/plugin.c:add_plugin() Loading sap plugin
bluetoothd[8075]: src/plugin.c:add_plugin() Loading a2dp plugin
bluetoothd[8075]: src/plugin.c:add_plugin() Loading avrcp plugin
bluetoothd[8075]: src/plugin.c:add_plugin() Loading network plugin
bluetoothd[8075]: src/plugin.c:add_plugin() Loading input plugin
bluetoothd[8075]: src/plugin.c:add_plugin() Loading hog plugin
bluetoothd[8075]: src/plugin.c:add_plugin() Loading health plugin
bluetoothd[8075]: src/plugin.c:add_plugin() Loading gap plugin
bluetoothd[8075]: src/plugin.c:add_plugin() Loading scanparam plugin
bluetoothd[8075]: src/plugin.c:add_plugin() Loading deviceinfo plugin
bluetoothd[8075]: src/plugin.c:add_plugin() Loading alert plugin
bluetoothd[8075]: src/plugin.c:add_plugin() Loading time plugin
bluetoothd[8075]: src/plugin.c:add_plugin() Loading proximity plugin
bluetoothd[8075]: src/plugin.c:add_plugin() Loading thermometer plugin
bluetoothd[8075]: src/plugin.c:add_plugin() Loading heartrate plugin
bluetoothd[8075]: src/plugin.c:add_plugin() Loading cyclingspeed plugin
bluetoothd[8075]: src/plugin.c:plugin_init() Loading plugins /home/vagrant/bluez-5.27/plugins/.libs
bluetoothd[8075]: src/plugin.c:add_plugin() Loading external_dummy plugin
bluetoothd[8075]: profiles/health/hdp.c:hdp_manager_start() Starting Health manager
bluetoothd[8075]: profiles/input/suspend-dummy.c:suspend_init()
bluetoothd[8075]: profiles/input/suspend-dummy.c:suspend_init() Created suspend-dummy FIFO on /tmp/hogsuspend
bluetoothd[8075]: profiles/network/manager.c:read_config() Config options: Security=true
bluetoothd[8075]: plugins/neard.c:neard_init() Setup neard plugin
bluetoothd[8075]: plugins/external-dummy.c:dummy_init()
bluetoothd[8075]: src/main.c:main() Entering main loop
bluetoothd[8075]: src/rfkill.c:rfkill_event() RFKILL event idx 0 type 2 op 0 soft 0 hard 0
bluetoothd[8075]: Bluetooth management interface 1.6 initialized
bluetoothd[8075]: src/adapter.c:read_version_complete() sending read supported commands command
bluetoothd[8075]: src/adapter.c:read_version_complete() sending read index list command
bluetoothd[8075]: src/adapter.c:read_commands_complete() Number of commands: 47
bluetoothd[8075]: src/adapter.c:read_commands_complete() Number of events: 23
bluetoothd[8075]: src/adapter.c:read_index_list_complete() Number of controllers: 1
bluetoothd[8075]: src/adapter.c:read_index_list_complete() Found index 0
bluetoothd[8075]: src/adapter.c:index_added() index 0
bluetoothd[8075]: src/adapter.c:btd_adapter_new() System name: BlueZ 5.27
bluetoothd[8075]: src/adapter.c:btd_adapter_new() Major class: 0
bluetoothd[8075]: src/adapter.c:btd_adapter_new() Minor class: 0
bluetoothd[8075]: src/adapter.c:btd_adapter_new() Modalias: usb:v1D6Bp0246d051B
bluetoothd[8075]: src/adapter.c:btd_adapter_new() Discoverable timeout: 180 seconds
bluetoothd[8075]: src/adapter.c:btd_adapter_new() Pairable timeout: 0 seconds
bluetoothd[8075]: src/adapter.c:index_added() sending read info command for index 0
bluetoothd[8075]: src/adapter.c:read_info_complete() index 0 status 0x00
bluetoothd[8075]: src/adapter.c:clear_uuids() sending clear uuids command for index 0
bluetoothd[8075]: src/attrib-server.c:btd_adapter_gatt_server_start() Start GATT server in hci0
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0001
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0004
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0006
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0007
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0008
bluetoothd[8075]: src/adapter.c:adapter_service_add() /org/bluez/hci0
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Adding record with handle 0x10001
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 00000007-0000-1000-8000-00805f9
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 00001800-0000-1000-8000-00805f9
bluetoothd[8075]: src/adapter.c:adapter_service_insert() /org/bluez/hci0
bluetoothd[8075]: src/adapter.c:add_uuid() sending add uuid command for index 0
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0010
bluetoothd[8075]: src/adapter.c:adapter_service_add() /org/bluez/hci0
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Adding record with handle 0x10002
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 00000007-0000-1000-8000-00805f9
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 00001801-0000-1000-8000-00805f9
bluetoothd[8075]: src/adapter.c:adapter_service_insert() /org/bluez/hci0
bluetoothd[8075]: src/adapter.c:add_uuid() sending add uuid command for index 0
bluetoothd[8075]: profiles/audio/a2dp.c:media_server_probe() path /org/bluez/hci0
bluetoothd[8075]: plugins/hostname.c:hostname_probe()
bluetoothd[8075]: attrib/gatt-service.c:gatt_service_add() New service: handle 0x0009, UUID a002, 4 attributes
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0009
bluetoothd[8075]: attrib/gatt-service.c:gatt_service_add() New characteristic: handle 0x000a
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x000a
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x000b
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x000c
bluetoothd[8075]: plugins/gatt-example.c:register_manuf1_service() start_handle=0x0011
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0011
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0012
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0013
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0014
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0015
bluetoothd[8075]: plugins/gatt-example.c:register_manuf2_service() start_handle=0x0016
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0016
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0017
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0018
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0019
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x001a
bluetoothd[8075]: plugins/gatt-example.c:register_termometer_service() start_handle=0x001b manuf1=0x0011-0x0015, manuf2=0x0016-0x001a
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x001b
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x001c
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x001d
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x001e
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x001f
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0020
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0021
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0022
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0023
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0024
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0025
bluetoothd[8075]: src/adapter.c:adapter_service_add() /org/bluez/hci0
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Adding record with handle 0x10003
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 00000007-0000-1000-8000-00805f9
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 0000a004-0000-1000-8000-00805f9
bluetoothd[8075]: src/adapter.c:adapter_service_insert() /org/bluez/hci0
bluetoothd[8075]: src/adapter.c:add_uuid() sending add uuid command for index 0
bluetoothd[8075]: plugins/gatt-example.c:register_vendor_service() start_handle=0x000d
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x000d
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x000e
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x000f
bluetoothd[8075]: plugins/gatt-example.c:register_weight_service() start_handle=0xfffa, vendor=0x000d-0x000f
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0xfffa
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0xfffb
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0xfffc
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0xfffd
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0xfffe
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0xffff
bluetoothd[8075]: src/adapter.c:adapter_service_add() /org/bluez/hci0
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Adding record with handle 0x10004
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 00000007-0000-1000-8000-00805f9
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Record pattern UUID feee74dc-a8de-3196-1149-d43596c
bluetoothd[8075]: src/adapter.c:adapter_service_insert() /org/bluez/hci0
bluetoothd[8075]: src/adapter.c:add_uuid() sending add uuid command for index 0
bluetoothd[8075]: attrib/gatt-service.c:gatt_service_add() New service: handle 0x0026, UUID 1803, 3 attributes
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0026
bluetoothd[8075]: attrib/gatt-service.c:gatt_service_add() New characteristic: handle 0x0027
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0027
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0028
bluetoothd[8075]: profiles/proximity/linkloss.c:link_loss_register() Link Loss service added
bluetoothd[8075]: profiles/proximity/reporter.c:register_tx_power() start_handle=0x0029
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0029
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x002a
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x002b
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x002c
bluetoothd[8075]: attrib/gatt-service.c:gatt_service_add() New service: handle 0x002d, UUID 1802, 3 attributes
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x002d
bluetoothd[8075]: attrib/gatt-service.c:gatt_service_add() New characteristic: handle 0x002e
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x002e
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x002f
bluetoothd[8075]: profiles/proximity/immalert.c:imm_alert_register() Immediate Alert service added
bluetoothd[8075]: profiles/proximity/reporter.c:reporter_adapter_probe() Proximity Reporter for adapter 0x95ebf28
bluetoothd[8075]: profiles/time/server.c:time_server_init() path /org/bluez/hci0
bluetoothd[8075]: attrib/gatt-service.c:gatt_service_add() New service: handle 0x0030, UUID 1805, 6 attributes
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0030
bluetoothd[8075]: attrib/gatt-service.c:gatt_service_add() New characteristic: handle 0x0031
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0031
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0032
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0033
bluetoothd[8075]: attrib/gatt-service.c:gatt_service_add() New characteristic: handle 0x0034
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0034
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0035
bluetoothd[8075]: attrib/gatt-service.c:gatt_service_add() New service: handle 0x0036, UUID 1806, 5 attributes
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0036
bluetoothd[8075]: attrib/gatt-service.c:gatt_service_add() New characteristic: handle 0x0037
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0037
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0038
bluetoothd[8075]: attrib/gatt-service.c:gatt_service_add() New characteristic: handle 0x0039
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0039
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x003a
bluetoothd[8075]: attrib/gatt-service.c:gatt_service_add() New service: handle 0x003b, UUID 180e, 9 attributes
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x003b
bluetoothd[8075]: attrib/gatt-service.c:gatt_service_add() New characteristic: handle 0x003c
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x003c
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x003d
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x003e
bluetoothd[8075]: attrib/gatt-service.c:gatt_service_add() New characteristic: handle 0x003f
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x003f
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0040
bluetoothd[8075]: attrib/gatt-service.c:gatt_service_add() New characteristic: handle 0x0041
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0041
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0042
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0043
bluetoothd[8075]: attrib/gatt-service.c:gatt_service_add() New service: handle 0x0044, UUID 1811, 13 attributes
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0044
bluetoothd[8075]: attrib/gatt-service.c:gatt_service_add() New characteristic: handle 0x0045
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0045
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0046
bluetoothd[8075]: attrib/gatt-service.c:gatt_service_add() New characteristic: handle 0x0047
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0047
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0048
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0049
bluetoothd[8075]: attrib/gatt-service.c:gatt_service_add() New characteristic: handle 0x004a
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x004a
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x004b
bluetoothd[8075]: attrib/gatt-service.c:gatt_service_add() New characteristic: handle 0x004c
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x004c
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x004d
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x004e
bluetoothd[8075]: attrib/gatt-service.c:gatt_service_add() New characteristic: handle 0x004f
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x004f
bluetoothd[8075]: src/attrib-server.c:attrib_db_add_new() handle=0x0050
bluetoothd[8075]: profiles/network/manager.c:panu_server_probe() path /org/bluez/hci0
bluetoothd[8075]: profiles/network/server.c:server_register() Registered interface org.bluez.NetworkServer1 on path /org/bluez/hci0
bluetoothd[8075]: profiles/network/manager.c:gn_server_probe() path /org/bluez/hci0
bluetoothd[8075]: profiles/network/manager.c:nap_server_probe() path /org/bluez/hci0
bluetoothd[8075]: profiles/audio/avrcp.c:avrcp_controller_server_probe() path /org/bluez/hci0
bluetoothd[8075]: src/adapter.c:adapter_service_add() /org/bluez/hci0
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Adding record with handle 0x10005
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 00000017-0000-1000-8000-00805f9
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 0000110e-0000-1000-8000-00805f9
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 0000110f-0000-1000-8000-00805f9
bluetoothd[8075]: src/adapter.c:adapter_service_insert() /org/bluez/hci0
bluetoothd[8075]: src/adapter.c:add_uuid() sending add uuid command for index 0
bluetoothd[8075]: profiles/audio/avrcp.c:avrcp_target_server_probe() path /org/bluez/hci0
bluetoothd[8075]: src/adapter.c:adapter_service_add() /org/bluez/hci0
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Adding record with handle 0x10006
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 00000017-0000-1000-8000-00805f9
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 0000110c-0000-1000-8000-00805f9
bluetoothd[8075]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 0000110e-0000-1000-8000-00805f9
bluetoothd[8075]: src/adapter.c:adapter_service_insert() /org/bluez/hci0
bluetoothd[8075]: src/adapter.c:add_uuid() sending add uuid command for index 0
bluetoothd[8075]: profiles/audio/a2dp.c:a2dp_sink_server_probe() path /org/bluez/hci0
bluetoothd[8075]: profiles/audio/a2dp.c:a2dp_source_server_probe() path /org/bluez/hci0
bluetoothd[8075]: profiles/sap/manager.c:sap_server_probe() path /org/bluez/hci0
**bluetoothd[8075]: Sap driver initialization failed.**
**bluetoothd[8075]: sap-server: Operation not permitted (1)**
bluetoothd[8075]: src/adapter.c:btd_adapter_unblock_address() hci0 00:00:00:00:00:00
bluetoothd[8075]: src/adapter.c:load_link_keys() hci0 keys 0 debug_keys 0
bluetoothd[8075]: src/adapter.c:load_ltks() hci0 keys 0
bluetoothd[8075]: src/adapter.c:load_irks() hci0 irks 0
bluetoothd[8075]: src/adapter.c:load_conn_params() hci0 conn params 0
bluetoothd[8075]: src/adapter.c:load_connections() sending get connections command for index 0
bluetoothd[8075]: src/adapter.c:adapter_service_insert() /org/bluez/hci0
bluetoothd[8075]: src/adapter.c:add_uuid() sending add uuid command for index 0
bluetoothd[8075]: src/adapter.c:set_did() hci0 source 2 vendor 1d6b product 246 version 51b
bluetoothd[8075]: src/adapter.c:adapter_register() Adapter /org/bluez/hci0 registered
bluetoothd[8075]: src/adapter.c:set_dev_class() sending set device class command for index 0
bluetoothd[8075]: src/adapter.c:set_name() sending set local name command for index 0
bluetoothd[8075]: src/adapter.c:set_mode() sending set mode command for index 0
bluetoothd[8075]: src/adapter.c:adapter_start() adapter /org/bluez/hci0 has been enabled
bluetoothd[8075]: src/adapter.c:trigger_passive_scanning()
bluetoothd[8075]: src/adapter.c:load_link_keys_complete() link keys loaded for hci0
bluetoothd[8075]: src/adapter.c:load_ltks_complete() LTKs loaded for hci0
bluetoothd[8075]: src/adapter.c:load_irks_complete() IRKs loaded for hci0
**bluetoothd[8075]: hci0 Load Connection Parameters failed: Unknown Command (0x01)**
bluetoothd[8075]: src/adapter.c:get_connections_complete() Connection count: 0
bluetoothd[8075]: plugins/hostname.c:property_changed() static hostname: jessie-i386
bluetoothd[8075]: plugins/hostname.c:property_changed() pretty hostname:
bluetoothd[8075]: plugins/hostname.c:update_name() name: jessie-i386
bluetoothd[8075]: src/adapter.c:adapter_set_name() name: jessie-i386
bluetoothd[8075]: src/adapter.c:adapter_set_name() alias: jessie-i386
bluetoothd[8075]: src/adapter.c:set_name() sending set local name command for index 0
bluetoothd[8075]: plugins/hostname.c:property_changed() chassis: vm
bluetoothd[8075]: src/adapter.c:local_name_changed_callback() Name: BlueZ 5.27
bluetoothd[8075]: src/adapter.c:local_name_changed_callback() Short name:
bluetoothd[8075]: src/adapter.c:local_name_changed_callback() Current alias: BlueZ 5.27
bluetoothd[8075]: src/attrib-server.c:attrib_db_update() handle=0x0006
bluetoothd[8075]: src/adapter.c:local_name_changed_callback() Name: jessie-i386
bluetoothd[8075]: src/adapter.c:local_name_changed_callback() Short name:
bluetoothd[8075]: src/adapter.c:local_name_changed_callback() Current alias: jessie-i386
bluetoothd[8075]: src/attrib-server.c:attrib_db_update() handle=0x0006
The Sap driver fails to initialize and I'm guessing that this causes the hci0 adapter to fail to load the connection parameters (see output).
The BlueZ 5.27 stack was built from the source code as follows:
./configure CFLAGS="$CFLAGS -Wno-sign-compare -Wno-format-security" --prefix=/usr --mandir=/usr/share/man --sysconfdir=/etc --localstatedir=/var --disable-systemd --enable-experimental --enable-maintainer-mode
make
sudo make install
No errors were reported during the build and installation.
Why is the Sap driver failing to initialize?
Thanks for any help you can provide.
After a reinstallation, it seems to have corrected itself. For the benefit of others, I'm listing how I installed, and got the example GATT server running:
My environment:
Vagrant
Virtual Box
Ubuntu Trusty Tahr as a guest OS (v. 14.04 32-bit OS)
Updated to linux kernel 3.16
Installed packages:
libglib2.0-dev
libdbus-1-dev
libudev-dev
libical-dev
libreadline-dev
Downloaded BlueZ 5.31 from here: https://www.kernel.org/pub/linux/bluetooth/bluez-5.31.tar.xz
Installation of updated kernel:
sudo apt-get update
sudo apt-get install --install-recommends linux-generic-lts-utopic
A reboot is necessary. I'm using Vagrant and lost shared folder access. If this happens to you, wait for vagrant to report the error and go into the VM anyway (vagrant ssh). In the VM, issue this command to fix the shared folder problem:
sudo /etc/init.d/vboxadd setup
I would reboot again (probably not necessary), to check that the shared folder is active again.
Once back in the VM, continue the installation of BlueZ 5.31:
cd ~
sudo apt-get install libglib2.0-dev libdbus-1-dev libudev-dev libical-dev libreadline-dev
wget https://www.kernel.org/pub/linux/bluetooth/bluez-5.31.tar.xz
tar xvf bluez-5.31.tar.xz
cd bluez-5.31
./configure --prefix=/usr --mandir=/usr/share/man --sysconfdir=/etc --localstatedir=/var --disable-systemd --enable-experimental --enable-maintainer-mode
make
sudo make install
sudo cp attrib/gatttool /usr/bin
Installation completed. Check it as follows:
hciconfig
You should get the follow response (or something similar):
hci0: Type: BR/EDR Bus: USB
BD Address: 00:1A:7D:DA:71:0C ACL MTU: 310:10 SCO MTU: 64:8
DOWN
RX bytes:15528 acl:126 sco:0 events:683 errors:0
TX bytes:6459 acl:146 sco:0 commands:234 errors:0
Bring up the Bluetooth adapter, start advertising, start example GATT server (heart rate service) with verbose on:
sudo hciconfig hci0 up
sudo tools/btmgmt -i hci0 advertising on
tools/gatt-server -i hci0 -s low -t public -r -v
Go to another device (I've used an iPod and another PC running BlueZ but having problems with Android devices) and connect to the service. Here is how I did it on another PC running BlueZ:
gatttool -b **MAC address of GATT server** -I
connect
primary
characteristics
You can issue other commands to read and write to the GATT server.
I love this forum finding many answers here. I hope this small contribution helps at least one other frustrated developer out there.
Related
What happened:
I have deployed ingress-Nginx using the HELM template. I have deployed a gRpc service and exposed it as ClusterIP service. The service.yaml can be seen. This gRpc service does not need any certificate. I have also created a Kubernetes Ingress. All these objects are getting created successfully. Below is the observation
Error while accessing the client
Grpc.Core.RpcException
HResult=0x80131500
Message=Status(StatusCode="Internal", Detail="Error starting gRPC call. HttpRequestException: An HTTP/2 connection could not be established because the server did not complete the HTTP/2 handshake.", DebugException="System.Net.Http.HttpRequestException: An HTTP/2 connection could not be established because the server did not complete the HTTP/2 handshake.
at System.Net.Http.HttpConnectionPool.ReturnHttp2Connection(Http2Connection connection, Boolean isNewConnection)
Ingress pod logs
I0109 02:18:30.699832 7 event.go:285] Event(v1.ObjectReference{Kind:"Pod", Namespace:"ingress-nginx", Name:"ingress-nginx-controller-6f7bd4bcfb-wchw5", UID:"bc4c59da-f378-421c-a12a-87d46fb6371d", APIVersion:"v1", ResourceVersion:"592645", FieldPath:""}): type: 'Normal' reason: 'RELOAD' NGINX reload triggered due to a change in configuration
W0109 02:18:37.595244 7 controller.go:1112] Service "grpc/grpc-file-service" does not have any active Endpoint.
W0109 02:18:40.928869 7 controller.go:1112] Service "grpc/grpc-file-service" does not have any active Endpoint.
In the second task, we can see that Nginx is not able to locate it. But the service exists in the namespace as the ingress
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/grpc-file-service ClusterIP 10.104.122.174 <none> 5288/TCP 13h
NAME ENDPOINTS AGE
endpoints/grpc-file-service 10.1.21.65:5288,10.1.21.66:5288 13h
**What you expected to happen**:
The gRPC handshake should happen. No error should happen
**NGINX Ingress controller version** (exec into the pod and run nginx-ingress-controller --version.):
NGINX Ingress controller
Release: v1.5.1
Build: d003aae913cc25f375deb74f898c7f3c65c06f05
Repository: https://github.com/kubernetes/ingress-nginx
nginx version: nginx/1.21.6
**Kubernetes version** (use `kubectl version`):
Client Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.2", GitCommit:"5835544ca568b757a8ecae5c153f317e5736700e", GitTreeState:"clean", BuildDate:"2022-09-21T14:33:49Z", GoVersion:"go1.19.1", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.0", GitCommit:"4ce5a8954017644c5420bae81d72b09b735c21f0", GitTreeState:"clean", BuildDate:"2022-05-03T13:38:19Z", GoVersion:"go1.18.1", Compiler:"gc", Platform:"linux/amd64"}
**Environment**:
- **Cloud provider or hardware configuration**: Local
- **OS** (e.g. from /etc/os-release): Widows 11
- **Kernel** (e.g. `uname -a`): NA
- **Install tools**: The cluster was created in Docker for Desktop kubernetes enabled (version Docker Desktop 4.15.0 (93002) )
- **Basic cluster related info**:
- `kubectl version`
`Client Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.2", GitCommit:"5835544ca568b757a8ecae5c153f317e5736700e", GitTreeState:"clean", BuildDate:"2022-09-21T14:33:49Z", GoVersion:"go1.19.1", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.0", GitCommit:"4ce5a8954017644c5420bae81d72b09b735c21f0", GitTreeState:"clean", BuildDate:"2022-05-03T13:38:19Z", GoVersion:"go1.18.1", Compiler:"gc", Platform:"linux/amd64"}`
- **How was the ingress-nginx-controller installed**:
- HELM
- `helm ls -A | grep -i ingress`
ingress-nginx ingress-nginx 1 2023-01-08 10:57:42.322980739 +0530 IST deployed ingress-nginx-4.4.2
1.5.1
- helm -n <ingresscontrollernamepspace> get values <helmreleasename>
USER-SUPPLIED VALUES: null
- command used to install ingress
helm upgrade --install ingress-nginx ingress-nginx --repo https://kubernetes.github.io/ingress-nginx --namespace ingress-nginx --create-namespace
- **Current State of the controller**:
- `kubectl describe ingressclasses`
Name: nginx
Labels: app.kubernetes.io/component=controller
app.kubernetes.io/instance=ingress-nginx
app.kubernetes.io/managed-by=Helm
app.kubernetes.io/name=ingress-nginx
app.kubernetes.io/part-of=ingress-nginx
app.kubernetes.io/version=1.5.1
helm.sh/chart=ingress-nginx-4.4.2
Annotations: meta.helm.sh/release-name: ingress-nginx
meta.helm.sh/release-namespace: ingress-nginx
Controller: k8s.io/ingress-nginx
Events: <none>
I am trying to launch a deployment object in k8s with kubernetes/redis image. But I am getting error Back-off restarting failed container. The issue occurs with just redis image and I am able to successfully run deployments with postgres image etc.
Here is the config file:
apiVersion: apps/v1
kind: Deployment
metadata:
name: redis-deployment
spec:
replicas: 1
selector:
matchLabels:
component: redis
template:
metadata:
labels:
component: redis
spec:
containers:
- name: redis
image: kubernetes/redis
ports:
- containerPort: 6379
Describe pod output:
Name: redis-deployment-57dcf8ff69-9v8sz
Namespace: default
Priority: 0
PriorityClassName: <none>
Node: minikube/10.0.2.15
Start Time: Sun, 10 Mar 2019 11:13:00 +0530
Labels: component=redis
pod-template-hash=57dcf8ff69
Annotations: <none>
Status: Running
IP: 172.17.0.8
Controlled By: ReplicaSet/redis-deployment-57dcf8ff69
Containers:
redis:
Container ID: docker://556544175a99da6cd704ddc5ae6e65ee0a424275872d86543bbfef6eebceff5b
Image: kubernetes/redis
Image ID: docker-pullable://kubernetes/redis#sha256:60e8254f473b1df64340da257e8e0a029c0ac67a76bdde296f11eba6cde515c7
Port: 6379/TCP
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 1
Started: Sun, 10 Mar 2019 20:12:26 +0530
Finished: Sun, 10 Mar 2019 20:13:28 +0530
Ready: False
Restart Count: 13
Environment: <none>
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from default-token-zqj5b (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
default-token-zqj5b:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-zqj5b
Optional: false
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 9h default-scheduler Successfully assigned default/redis-deployment-57dcf8ff69-9v8sz to minikube
Normal Pulling 5h (x5 over 9h) kubelet, minikube pulling image "kubernetes/redis"
Normal Pulled 5h (x5 over 5h) kubelet, minikube Successfully pulled image "kubernetes/redis"
Normal Created 5h (x5 over 5h) kubelet, minikube Created container
Normal Started 5h (x5 over 5h) kubelet, minikube Started container
Warning BackOff 5h (x53 over 5h) kubelet, minikube Back-off restarting failed container
Normal SandboxChanged 17m kubelet, minikube Pod sandbox changed, it will be killed and re-created.
Normal Pulling 11m (x4 over 16m) kubelet, minikube pulling image "kubernetes/redis"
Normal Pulled 11m (x4 over 16m) kubelet, minikube Successfully pulled image "kubernetes/redis"
Normal Created 11m (x4 over 16m) kubelet, minikube Created container
Normal Started 11m (x4 over 16m) kubelet, minikube Started container
Warning BackOff 1m (x39 over 15m) kubelet, minikube Back-off restarting failed container
I am using the kubernetes/redis image in this example as using redis image completely fails because kubectl is not able to get the image pulled from dockerhub and I get the error which says failed in pulling the image. Not sure why !
Can anyone please help me out here.
EDIT---
Logs
kubectl.exe logs redis-deployment-57dcf8ff69-9v8sz
Could not connect to Redis at -p:6379: Name or service not known
Failed to find master.
Below config file worked for me.
apiVersion: apps/v1
kind: Deployment
metadata:
name: redis-deployment
spec:
replicas: 1
selector:
matchLabels:
component: redis
template:
metadata:
labels:
component: redis
spec:
containers:
- name: redis
image: gcr.io/google_containers/redis:v1
env:
- name: MASTER
value: "true"
ports:
- containerPort: 6379
How To Mount USD External Storage Drive on to ESXi 5.5 Host for VM backup
After USB Drive plugin, "esxcli storage core device list" shows there is a usb drive attached. But unable to access it.
"esxcli storage core device list "
mpx.vmhba38:C0:T0:L0
Display Name: Local USB Direct-Access (mpx.vmhba38:C0:T0:L0)
Has Settable Display Name: false
Size: 1907729
Device Type: Direct-Access
Multipath Plugin: NMP
Devfs Path: /vmfs/devices/disks/mpx.vmhba38:C0:T0:L0
Vendor: Seagate
Model: BUP Slim BL
Revision: 0108
SCSI Level: 2
Is Pseudo: false
Status: on
Is RDM Capable: false
Is Local: true
Is Removable: true
Is SSD: false
Is Offline: false
Is Perennially Reserved: false
Queue Full Sample Size: 0
Queue Full Threshold: 0
Thin Provisioning Status: unknown
Attached Filters:
VAAI Status: unsupported
Other UIDs: vml.0000000000766d68626133383a303a30
Is Local SAS Device: false
Is USB: true
Is Boot USB Device: false
No of outstanding IOs with competing worlds: 32
"esxcli storage core path list -d mpx.vmhba38:C0:T0:L0"
usb.vmhba38-usb.0:0-mpx.vmhba38:C0:T0:L0
UID: usb.vmhba38-usb.0:0-mpx.vmhba38:C0:T0:L0
Runtime Name: vmhba38:C0:T0:L0
Device: mpx.vmhba38:C0:T0:L0
Device Display Name: Local USB Direct-Access (mpx.vmhba38:C0:T0:L0)
Adapter: vmhba38
Channel: 0
Target: 0
LUN: 0
Plugin: NMP
State: active
Transport: usb
Adapter Identifier: usb.vmhba38
Target Identifier: usb.0:0
Adapter Transport Details: Unavailable or path is unclaimed
Target Transport Details: Unavailable or path is unclaimed
Maximum IO Size: 122880
Note: I stopped usbarbitrator.
/etc/init.d/usbarbitrator status
usbarbitrator is not running
Please advice.
There are very few USB drives that work directly against an ESXi host, and versions prior to 6.0 had a very strict ruleset against mounting unsupported devices.
I'm assuming you're attempting to mount the USB drive as a VMFS volume, which is unsupported regardless of what version, however there is a list of supported devices that work for passthrough activities. I would assume these could be used as VMFS mounts as well: https://kb.vmware.com/kb/1021345
While it looks like you're following the proper steps, here's a detailed list that may help: https://kb.vmware.com/s/article/2065934
Alternatively, since USB performance is generally pretty slow on ESXi hosts, you could also perform your backup activities on the VM and then SCP the files off the ESXi host to the USB drive.
I have a website with a letsencrypt ssl cert. When I ran codeception acceptance tests against it, the test stalls until I press ctrl+z. When I ran the same test against a non ssl site, there is no problem.
That is my setup in acceptance.suite.yml. The phantomjs.cli.args paramater is from this site: http://szdredd.blogspot.de/2013/10/codeception-phantomjs-setup-for.html
class_name: AcceptanceTester
modules:
enabled: [WebDriver]
config:
WebDriver:
url: https://www.domain.de/
browser: phantomjs
My selenium log looks like this:
17:07:15.681 INFO - Executing: [new session: Capabilities [{browserName=phantomjs}]])
17:07:15.682 INFO - Creating a new session for Capabilities [{browserName=phantomjs}]
17:07:15.682 INFO - executable: /usr/bin/phantomjs
17:07:15.683 INFO - port: 27757
17:07:15.683 INFO - arguments: [--webdriver=27757, --webdriver-logfile=/phantomjsdriver.log]
17:07:15.683 INFO - environment: {}
PhantomJS is launching GhostDriver...
[INFO - 2016-02-20T17:07:15.754Z] GhostDriver - Main - running on port 27757
[INFO - 2016-02-20T17:07:15.765Z] Session [64316920-d7f4-11e5-a0c5-8954be0ea076] - CONSTRUCTOR - Desired Capabilities: {"browserName":"phantomjs"}
[INFO - 2016-02-20T17:07:15.765Z] Session [64316920-d7f4-11e5-a0c5-8954be0ea076] - CONSTRUCTOR - Negotiated Capabilities: {"browserName":"phantomjs","version":"1.9.0","driverName":"ghostdriver","driverVersion":"1.0.3","platform":"linux-unknown-64bit","javascriptEnabled":true,"takesScreenshot":true,"handlesAlerts":false,"databaseEnabled":false,"locationContextEnabled":false,"applicationCacheEnabled":false,"browserConnectionEnabled":false,"cssSelectorsEnabled":true,"webStorageEnabled":false,"rotatable":false,"acceptSslCerts":false,"nativeEvents":true,"proxy":{"proxyType":"direct"}}
[INFO - 2016-02-20T17:07:15.765Z] SessionManagerReqHand - _postNewSessionCommand - New Session Created: 64316920-d7f4-11e5-a0c5-8954be0ea076
17:07:15.771 INFO - Done: [new session: Capabilities [{browserName=phantomjs}]]
17:07:15.774 INFO - Executing: [implicitly wait: 0])
17:07:15.777 INFO - Done: [implicitly wait: 0]
17:07:15.790 INFO - Executing: [get: https://www.waldhelden.de/])
[INFO - 2016-02-20T17:07:33.916Z] SessionManagerReqHand - _cleanupWindowlessSessions - Asynchronous Sessions clean-up phase starting NOW
[INFO - 2016-02-20T17:08:55.442Z] SessionManagerReqHand - _cleanupWindowlessSessions - Asynchronous Sessions clean-up phase starting NOW
[INFO - 2016-02-20T17:09:02.008Z] SessionManagerReqHand - _cleanupWindowlessSessions - Asynchronous Sessions clean-up phase starting NOW
17:09:13.204 INFO - Session 7c5ef02c-9361-49c8-894d-234989179189 deleted due to client timeout
[INFO - 2016-02-20T17:09:13.211Z] ShutdownReqHand - _handle - About to shutdown
I found an advise on this side, but when I add that configuration I an error:
capabilities:
phantomjs.cli.args: ['--ignore-ssl-errors=true']
Caused by: org.openqa.selenium.WebDriverException: The best matching driver provider org.openqa.selenium.htmlunit.HtmlUnitDriver can't create a new driver instance for Capabilities [{phantomjs.cli.args=[--ignore-ssl-errors=true], browserName=phantom}]
Who knows how to setup codeception to ignore ssl errors? Any help appreciated!
Thanks
Udo
For testing my site I use Phantoman to automatically run and close phantomJS. In codeception.yml I have:
config:
Codeception\Extension\Phantoman:
path: 'vendor/bin/phantomjs'
port: 4444
debug: true
ignoreSslErrors: true
sslProtocol: any
Codeception\Extension\Recorder:
delete_successful: true
I have started glassfish server in netbeans, but cant't have access to admin console through web brouser on localhost:4848
The log of start up process:
21.01.2011 18:48:34 com.sun.enterprise.glassfish.bootstrap.ASMain main
INFO: Launching GlassFish on Felix platform
Welcome to Felix
================
INFO: Perform lazy SSL initialization for the listener 'http-listener-1'
INFO: Perform lazy SSL initialization for the listener 'http-listener-2'
INFO: Perform lazy SSL initialization for the listener 'admin-listener'
INFO: Starting Grizzly Framework 1.9.18-k - Fri Jan 21 18:48:37 EET 2011
INFO: The Admin Console is already installed, but not yet loaded.
INFO: Grizzly Framework 1.9.18-k started in: 219ms listening on port 8181
INFO: Grizzly Framework 1.9.18-k started in: 203ms listening on port 4848
INFO: Grizzly Framework 1.9.18-k started in: 235ms listening on port 8080
INFO: Starting Grizzly Framework 1.9.18-k - Fri Jan 21 18:48:37 EET 2011
INFO: Grizzly Framework 1.9.18-k started in: 906ms listening on port 3700
INFO: Grizzly Framework 1.9.18-k started in: 891ms listening on port 7676
INFO: GlassFish v3 (74.2) startup time : Felix(2422ms) startup services(1890ms) total(4312ms)
INFO: javassist.util.proxy.ProxyFactory.classLoaderProvider = org.glassfish.weld.WeldActivator$GlassFishClassLoaderProvider#1fa2b3e
INFO: Hibernate Validator bean-validator-3.0-JBoss-4.0.2
INFO: Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
INFO: Binding RMI port to *:8686
INFO: JMXStartupService: Started JMXConnector, JMXService URL = service:jmx:rmi://localhost:8686/jndi/rmi://localhost:8686/jmxrmi
INFO: Using com.sun.enterprise.transaction.jts.JavaEETransactionManagerJTSDelegate as the delegate
INFO: Perform lazy SSL initialization for the listener 'http-listener-1'
INFO: Grizzly Framework 1.9.18-k started in: 0ms listening on port 8080
INFO: [Thread[GlassFish Kernel Main Thread,5,main]] started
INFO: {felix.fileinstall.poll (ms) = 5000, felix.fileinstall.dir = C:\Program Files\sges-v3\glassfish\modules\autostart, felix.fileinstall.debug = 1, felix.fileinstall.bundles.new.start = true, felix.fileinstall.tmpdir = C:\DOCUME~1\Admin\LOCALS~1\Temp\fileinstall-6018388012782185995, felix.fileinstall.filter = null}
INFO: Perform lazy SSL initialization for the listener 'http-listener-2'
INFO: {felix.fileinstall.poll (ms) = 5000, felix.fileinstall.dir = C:\Program Files\sges-v3\glassfish\domains\domain1\autodeploy\bundles, felix.fileinstall.debug = 1, felix.fileinstall.bundles.new.start = true, felix.fileinstall.tmpdir = C:\DOCUME~1\Admin\LOCALS~1\Temp\fileinstall-570365091622749624, felix.fileinstall.filter = null}
INFO: Grizzly Framework 1.9.18-k started in: 16ms listening on port 8181
INFO: Updating configuration from org.apache.felix.fileinstall-autodeploy-bundles.cfg
INFO: Installed C:\Program Files\sges-v3\glassfish\modules\autostart\org.apache.felix.fileinstall-autodeploy-bundles.cfg
INFO: {felix.fileinstall.poll (ms) = 5000, felix.fileinstall.dir = C:\Program Files\sges-v3\glassfish\domains\domain1\autodeploy\bundles, felix.fileinstall.debug = 1, felix.fileinstall.bundles.new.start = true, felix.fileinstall.tmpdir = C:\DOCUME~1\Admin\LOCALS~1\Temp\fileinstall--7403987252271825379, felix.fileinstall.filter = null}
How can i have access to console?
edited:
It is available on https://localhost:4848
How i can change it to http://localhost:4848
Here is a thousand words... and then some...
I got same issue. It worked/browsed earlier.
I felt that there is some goof up in internet explorer in Windows 7.
I just changed to the latest version of Google Chrome, and it just worked.