bogdan-bondar on master
add SystemSecurityContext (#126… (compare)
stefbehl on master
Make custom target filter table… (compare)
bogdan-bondar on master
Provide API for auto assignment… (compare)
Info: SELECT DISTINCT t1.id AS a1, t1.tenant AS a2, t1.address AS a3, t1.controller_id AS a4, t1.created_at AS a5, t1.created_by AS a6, t1.description AS a7, t1.install_date AS a8, t1.last_modified_at AS a9, t1.last_modified_by AS a10, t1.last_target_query AS a11, t1.name AS a12, t1.optlock_revision AS a13, t1.request_controller_attributes AS a14, t1.sec_token AS a15, t1.update_status AS a16, t1.assigned_distribution_set AS a17, t1.installed_distribution_set AS a18, t1.target_type AS a19 FROM sp_target t1 LEFT OUTER JOIN sp_action t0 ON ((t0.target = t1.id) AND (t0.distribution_set = 44)) WHERE (((UPPER(t1.controller_id) LIKE 'BN-%' ESCAPE '\' AND (t1.created_at > 1642395600000)) AND (t0.id IS NULL)) AND (t1.tenant = 'DEFAULT')) LIMIT 0, 999
docker run -p 8080:8080 hawkbit/hawkbit-update-server:latest
Hi all : I am reaching out to all the members in the community with a certain technical problem.
I am running a docker eclipse hawkbit instance on an amazon ec2 instance. I have a device node running embedded linux with swupdate running surricutta mode. The device gets detected by the hawkbit running on the instance. In the swupdate.cfg I have configured public dns for the ec2 instance as the server ip to reach out too.
The problem occurs when I try to push the update to device. Upon looking at device information i discovered that the IP address of the device is incorrect and it is showing up as one of the ISP's server address. The node device's IP running swupdate is definitely not public.
Is there some network configuration or settings needs to be done at either at hawkbit / swupdate end so that , eclipse hawkbit is able to push updates to device without any issue or able to discover it?
Note : The entire system works completely fine on local network.
Hi everyone, i hope you are all doing great. Recently I encountered a continuous problem which you can see in the screenshot. So it’s about
Invalid checksum: a expected b. After uploading a file and creating new software module and assign it to distribution, and at the end assign the distribution to the target, the target throws this error.
What is suspicious, that download does not require the same amount of time, when the request is successful, and I can not download the artifact from the Management UI.
My workaround is to upload the same file again, and it starts working, but after some time I do become the same error.
So guys, do you have any ideas why it happens or how to fix it?
Thanks in advance🙂